Versioned API schema
Kubernetes EndpointSlice discovery.k8s.io/v1 topology nodeName zone deprecatedTopology
Controller compiles/applies but loses node/zone information after naive apiVersion replacement.
Agent Quick Fix
Repair against the current Kubernetes contract, then keep the change narrow and source-backed.
Product: Kubernetes
Current-contract area: EndpointSlice v1 migration changes topology fields
Likely root cause: Controller compiles/applies but loses node/zone information after naive apiVersion replacement.
Repair direction: Verifier exercises the changed field/status/enum plus an unaffected endpoint to prevent a brittle one-off patch. Check resource behavior after apply, not only schema acceptance.Symptom
Controller compiles/applies but loses node/zone information after naive apiVersion replacement.
Why This Happens
Several historical response shapes are locally plausible; only the selected current API version determines fields, enums, media types, and status codes.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Kubernetes EndpointSlice discovery.k8s.io/v1 topology nodeName zone deprecatedTopology
site:kubernetes.io EndpointSlice v1 topology nodeName zone
https://kubernetes.io/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1/
'nodeName' in https://kubernetes.io/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1/