Kubernetes has officially deprecated the Endpoints API as of version 1.33, encouraging users to adopt the more advanced EndpointSlices. This transition began with the introduction of EndpointSlices in alpha in version 1.15 and achieved general availability in version 1.21. This change significantly alters how services manage network endpoints.
The Endpoints API has lost relevance as new features—such as dual-stack networking and improved traffic distribution—are only available through EndpointSlices. Consequently, service proxies and various controllers have shifted from the Endpoints API to utilize EndpointSlices, which provide enhanced functionality.
With this deprecation, attempts to access Endpoints resources will result in warnings, prompting users to migrate their workloads and scripts to the EndpointSlices API. The Kubernetes development team plans to revise the Conformance criteria, potentially dropping the requirement for running the Endpoints controller in most current clusters.
Key Adjustments for Users
For users, the key adjustment involves how services and their associated endpoints are represented. Unlike the single Endpoints object corresponding to a service, EndpointSlices support multiple instances per service. This advantage is especially relevant for:
- Dual-stack services – which can have separate slices for IPv4 and IPv6 addresses.
Migration Process
Migrating from Endpoints to EndpointSlices requires changes in both command-line interactions and supporting code. Users must modify how they query and manage endpoints, including employing labels to retrieve EndpointSlices linked to specific services.
As Kubernetes evolves, adapting to these changes enables users to maximize the full spectrum of functionalities offered by the new API, ensuring their applications stay current with the platform’s innovations.
For further details, visit the Kubernetes blog.
