Kubernetes / Services, DNS & Traffic Routing
Diagnose NodePort reachability across node and application layers
A NodePort path depends on node reachability, Service mapping and eligible endpoints. Inspect the actual allocated port rather than guessing.
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.type}{" "}{.spec.ports}'Read the result
The output identifies the Service type and assigned ports. It does not prove a firewall permits access or every node is intended as an ingress endpoint.
Resolve and verify
Compare the approved client path, traffic policy and EndpointSlices with node networking evidence. Repair the narrow mapping or infrastructure rule and test the real service.
Before changing production
Do not open the entire NodePort range publicly to make one workload reachable.