Kubernetes / Services, DNS & Traffic Routing
Check Service IP families during an IPv4 or IPv6-only failure
A client may select an address family that the workload or cluster path does not support. Inspect the Service's actual family configuration.
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.ipFamilies}{" "}{.spec.ipFamilyPolicy}{" "}{.spec.clusterIPs}'Read the result
The fields describe requested and allocated Service family behavior. Node, CNI and external provider support are separate requirements.
Resolve and verify
Compare client DNS selection and backend listener families with the supported cluster design. Repair the failing path and test each intended family.
Before changing production
Do not disable IPv6 cluster-wide or assume an allocated second IP proves every application handles it.