Kubernetes / Services, DNS & Traffic Routing
Explain node-dependent behavior with externalTrafficPolicy Local
A request can succeed through nodes with local endpoints and fail through others when local traffic policy is intentional.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app get service web -o jsonpath='{.spec.externalTrafficPolicy}'
kubectl -n app get pods -o wideRead the result
The policy and Pod placement give context, but load-balancer health checks and published endpoints determine the actual traffic path.
Resolve and verify
Compare source-IP preservation goals with local endpoint availability and provider health checks. Correct placement or routing through the supported design and verify failover.
Before changing production
Do not change traffic policy without reviewing source-address, load distribution and availability effects.