Kubernetes Kubectl Silently Shows Endpoints: None on EndpointSlice List Failure
Is it fixed? Not yet.
Ongoing since Nov 16, 10:50 UTC. First reported Nov 16, 10:50 UTC.
What happened
Kubectl's ServiceDescriber silently ignores errors returned when listing EndpointSlices, resulting in Endpoints: <none> being printed for each port instead of surfacing the failure. This affects users attempting to describe services without permissions to list endpointslices. Currently, the issue has been reported in the GitHub repository.
What caused it?
ServiceDescriber.Describe in staging/src/k8s.io/kubectl/pkg/describe/describe.go ignores the error returned when calling d.DiscoveryV1().EndpointSlices(service.Namespace).List(...).
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on GitHub issue
kubectl describe service silently shows Endpoints: <none> when listing EndpointSlices fails
Source
Evidence
1 report · 1 GitHubShow
- [1]GitHub First reportkubectl describe service silently shows Endpoints: <none> when listing EndpointSlices fails(opens GitHub issue in a new tab)
What happened? ServiceDescriber.Describe in staging/src/k8s.io/kubectl/pkg/describe/describe.go ignores the error returned when listing EndpointSlices: endpointSliceList, _ := d.DiscoveryV1().EndpointSlices(service.Namespace).List(...) If the list call fails (for example Forbidden because the user can get services but not list endpointslices), describe returns no error and prints Endpoints: <none> for each port. I reproduced this with a fake clientset whose list endpointslices reactor returns…
by harshal-paltse 0upvotes 2comments
FAQ
What happened in the Kubernetes outage?
Kubectl's ServiceDescriber silently ignores errors returned when listing EndpointSlices, resulting in Endpoints: <none> being printed for each port instead of surfacing the failure. This affects users attempting to describe services without permissions to list endpointslices. Currently, the issue has been reported in the GitHub repository.
What is affected by the Kubernetes outage?
Kubernetes. Also affected at the same time: GitHub.
When did the Kubernetes outage start and end?
It started Nov 16, 10:50 UTC and is still ongoing (2 d 17 h so far). This page updates as it develops.
How do I get alerts for Kubernetes?
Subscribe to the Kubernetes RSS feed for every new Kubernetes incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Kubernetes is down. Kubernetes feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.