Skip to content

Warning: v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice #15561

Description

@Sweatha-g

What is the issue?

Hi I am on EKS 1.34 version and My linkerd Creds and Control plane are on linkerd-edge -version 2026.7.2 .
I have been seeing the below message in my logs and it's kind of flooding

level=info msg="Warning: v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice"

I knew this is an info/warning But is linkerd still querying on Endpoints instead of Endpointslices

How can it be reproduced?

Install linkerd2-edge 2026.7.2 on EKS 1.34 . Observe warnings in linkerd-destination:

level=info msg="Warning: v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice"

Logs, error output, etc

level=info msg="Warning: v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice"

output of linkerd check -o short

linkerd-version

‼ cli is up-to-date
is running version 26.5.2 but the latest edge version is 26.8.1
see https://linkerd.io/2/checks/#l5d-version-cli for hints

control-plane-version

‼ control plane is up-to-date
is running version 26.7.2 but the latest edge version is 26.8.1
see https://linkerd.io/2/checks/#l5d-version-control for hints
‼ control plane and cli versions match
control plane running edge-26.7.2 but cli running edge-26.5.2
see https://linkerd.io/2/checks/#l5d-version-control for hints

linkerd-control-plane-proxy

‼ control plane proxies are up-to-date
some proxies are not running the current version:
* linkerd-destination-78b7469454-zv4ct (edge-26.7.2)
* linkerd-identity-66f5cbbd6f-tkwb2 (edge-26.7.2)
* linkerd-proxy-injector-79df8c4f84-cwgrm (edge-26.7.2)
see https://linkerd.io/2/checks/#l5d-cp-proxy-version for hints
‼ control plane proxies and cli versions match
linkerd-destination-78b7469454-zv4ct running edge-26.7.2 but cli running edge-26.5.2
see https://linkerd.io/2/checks/#l5d-cp-proxy-cli-version for hints

Status check results are √

Environment

EKS 1.34
Linkerd- Linkerd2-edge 2026.7.2

Possible solution

No response

Additional context

No response

Would you like to work on fixing this bug?

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions