NodePort service type in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding NodePort Service Exposure

What is the primary purpose of a NodePort service in Kubernetes?

A To expose a service on a static port on each node's IP, allowing external traffic to access the service.

B To expose a service only via DNS inside the cluster.

C To automatically assign a load balancer IP from a cloud provider.

D To create an internal-only service accessible only within the cluster.

💡 Hint

Think about how external users can reach a service running inside Kubernetes nodes.

A NodePort service opens a specific port on every node in the cluster. This port forwards traffic to the service, allowing external access through any node's IP and that port.

💻 Command Output

intermediate

NodePort Service Port Range

What is the default port range for NodePort services in Kubernetes?

A 80-8080

B 1024-65535

C 1-1023

D 30000-32767

💡 Hint

NodePort ports are usually in a high range to avoid conflicts with well-known ports.

Kubernetes reserves ports 30000 to 32767 for NodePort services by default to avoid conflicts with system ports.

❓ Configuration

advanced

Correct NodePort Service YAML

Which YAML snippet correctly defines a NodePort service exposing port 8080 on target pods?

A

apiVersion: v1
kind: Service
metadata:
  name: my-nodeport-service
spec:
  type: NodePort
  selector:
    app: myapp
  ports:
    - port: 8080
      targetPort: 8080
      nodePort: 30080

B

apiVersion: v1
kind: Service
metadata:
  name: my-nodeport-service
spec:
  type: ClusterIP
  selector:
    app: myapp
  ports:
    - port: 8080
      targetPort: 8080
      nodePort: 30080

C

apiVersion: v1
kind: Service
metadata:
  name: my-nodeport-service
spec:
  type: NodePort
  selector:
    app: myapp
  ports:
    - port: 80
      targetPort: 8080
      nodePort: 30080

D

apiVersion: v1
kind: Service
metadata:
  name: my-nodeport-service
spec:
  type: NodePort
  selector:
    app: myapp
  ports:
    - port: 8080
      targetPort: 80
      nodePort: 30080

💡 Hint

Check that the service type is NodePort and ports match the target pod port.

Option A correctly sets the service type to NodePort, exposes port 8080, and maps nodePort 30080 to targetPort 8080 on pods.

❓ Troubleshoot

advanced

NodePort Service Not Accessible Externally

You created a NodePort service on port 30080, but external clients cannot access it. Which is the most likely cause?

A The service type is incorrectly set to ClusterIP.

B The cluster nodes' firewall is blocking port 30080.

C The pod selector labels do not match any pods.

D The nodePort value is outside the allowed range.

💡 Hint

Think about network rules outside Kubernetes that might block traffic.

Even if Kubernetes exposes the port, external firewalls on nodes can block incoming traffic, preventing access.

✅ Best Practice

expert

Best Practice for NodePort Usage in Production

Which practice is recommended when using NodePort services in a production Kubernetes environment?

A Expose NodePort services on all nodes without any firewall restrictions.

B Always assign nodePort values below 1024 for better compatibility.

C Use NodePort only for development or testing; use LoadBalancer or Ingress for production traffic.

D Use NodePort services to expose database ports directly to the internet.

💡 Hint

Consider security and scalability for production environments.

NodePort is simple but less secure and scalable. LoadBalancer or Ingress controllers provide better production-grade traffic management.