You are viewing documentation for Kubernetes version: v1.18

Kubernetes v1.18 documentation is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.

Edit This Page

Enabling EndpointSlices

This page provides an overview of enabling EndpointSlices in Kubernetes.

Before you begin

You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. If you do not already have a cluster, you can create one by using Minikube, or you can use one of these Kubernetes playgrounds:

To check the version, enter kubectl version.


EndpointSlices provide a scalable and extensible alternative to Endpoints in Kubernetes. They build on top of the base of functionality provided by Endpoints and extend that in a scalable way. When Services have a large number (>100) of network endpoints, they will be split into multiple smaller EndpointSlice resources instead of a single large Endpoints resource.

Enabling EndpointSlices

FEATURE STATE: Kubernetes v1.17 [beta]
Note: Although EndpointSlices may eventually replace Endpoints, many Kubernetes components still rely on Endpoints. For now, enabling EndpointSlices should be seen as an addition to Endpoints in a cluster, not a replacement for them.

EndpointSlices are a beta feature. Both the API and the EndpointSlice ControllerA control loop that watches the shared state of the cluster through the apiserver and makes changes attempting to move the current state towards the desired state. are enabled by default. kube-proxykube-proxy is a network proxy that runs on each node in the cluster. uses Endpoints by default, not EndpointSlices.

For better scalability and performance, you can enable the EndpointSliceProxying feature gate on kube-proxy. That change switches the data source to be EndpointSlices, which reduces the amount of Kubernetes API traffic to and from kube-proxy.

Using EndpointSlices

With EndpointSlices fully enabled in your cluster, you should see corresponding EndpointSlice resources for each Endpoints resource. In addition to supporting existing Endpoints functionality, EndpointSlices include new bits of information such as topology. They will allow for greater scalability and extensibility of network endpoints in your cluster.

What's next