In a VKE cluster, a workload is unbound from a Service (Kubernetes Service) in the console, or the associated selector labels of the Service are cleared.

Accessing the address of the Service can still reach the previously associated workload.

Cause

This issue occurs due to unreasonable design logic in the native Kubernetes EndpointSlice controller. For more information, see the Community documentation.

Solution

If you no longer need the Service, delete it. For details, see Deleting Services.

To change the association between a Service and a workload, replace the original workload with a new workload directly. For details, see Updating Services and Editing Service YAML files.

Last updated: 2026.07.23 14:31:45

Public security network record in Beijing: No. 11010802032137