Skip to content

EndpointSlice controllers should ignore EndpointSlices that are in a terminating state #108779

@robscott

Description

@robscott

What happened?

As discussed in #108267, Endpoint(Slice) controllers can get stuck if an Endpoints or EndpointSlice resource is stuck in a terminating state.

What did you expect to happen?

I don't think there's much we can do for Endpoints here since the same name is reused, but EndpointSlice controllers can ignore EndpointSlices in a terminating state.

How can we reproduce it (as minimally and precisely as possible)?

See #108267

Anything else we need to know?

No response

Kubernetes version

All supported versions

Cloud provider

Any

OS version

Any

Install tools

Any

Container runtime (CRI) and version (if applicable)

Any

Related plugins (CNI, CSI, ...) and versions (if applicable)

Any

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.sig/networkCategorizes an issue or PR as relevant to SIG Network.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions