The Kubernetes Endpoints API is now deprecated as of version 1.33, with warnings issued for its usage, as EndpointSlices offer more features. New Service features like dual-stack networking are only supported by EndpointSlices. The plan is to eventually remove the requirement for clusters to run the Endpoints controller. Users with existing Endpoints API workloads should migrate to EndpointSlices. Unlike Endpoints, a Service can have multiple EndpointSlices, especially for dual-stack networking or when exceeding 100 endpoints. EndpointSlices are retrieved by label, not name, using "kubernetes.io/service-name". Generating EndpointSlices involves using the new API type and organizing information differently. EndpointSlices require explicit address type declaration (IPv4 or IPv6). Each address array in an EndpointSlice by convention contains a single element. The EndpointSlice API provides conditions like "ready: false" for endpoints and supports topology hints.