Error AtlasError Documentation and Resolution

GKE could not schedule the pod because nodes did not have free requested pod ports

0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports.

GKE could not place the pod on a node because the requested hostPort is already in use and the node does not have a free matching port.

0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports.networking
0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports.
  • Multiple pods on the same node are trying to use the same hostPort value.
  • The workload relies on hostPort, which limits scheduling flexibility.
  • The current node set does not have any free host ports matching the pod requirements.
  1. Review pod manifests and make sure hostPort values are unique where required.
  2. Prefer NodePort or other service patterns instead of hostPort where possible.
  3. Reschedule or redesign the workload so it does not require conflicting host port bindings.
Google Cloud: Troubleshoot issues with deployed workloads in GKE
GKE didn't have free ports for the requested pod ports: causes and fixes | Error Atlas