Question

You are exposing a legacy monitoring application on a bare-metal cluster using a Service of type NodePort. You attempt to apply the following manifest, which explicitly requests nodePort 8080, but the API server rejects it with a validation error: 'provided port is not in the valid range. The range of valid ports is 30000-32767'. The application inside the Pod listens on container port 8080, and the Service targetPort is set to 8080. What is the correct way to resolve this while keeping the Service type as NodePort?

Accepted Answer

Change the nodePort value to a port within 30000-32767 (or omit nodePort to let Kubernetes auto-assign one), keeping targetPort at 8080.

Answer

Set targetPort to a value in the 30000-32767 range so it matches the required nodePort range.

Answer

Edit the container's listening port to be within 30000-32767 and update targetPort accordingly.

Answer

Add the annotation service.beta.kubernetes.io/node-port-range: '1-65535' to the Service to override the default range.