Review pod specifications for hostPort requests
Check whether your pods specify a hostPort. When multiple pods request the same port, Kubernetes schedules each pod onto its own node to avoid port conflicts.

Remove the hostPort request when possible
Avoid using hostPort unless you have a specific requirement for it. Kubernetes best practices recommend avoiding hostPort because it ties pods to specific nodes and reduces scheduling flexibility.

Use alternatives such as NodePort or port forwarding
If you only need to expose a local port for debugging or testing, consider using port forwarding instead of hostPort.
For example, you can run:

kubectl port-forward deployment/<name> 8080:80

Refer to Kubernetes configuration best practices for guidance
For additional context and best practices, see the Kubernetes documentation on configuration and networking.