ClusterIP service type in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

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

Choose the best description of what a ClusterIP service does inside a Kubernetes cluster.

A It assigns a static IP address to a pod for external access.

B It exposes the service externally using a cloud provider's load balancer.

C It creates a DNS record that points to an external IP address outside the cluster.

D It exposes the service on a cluster-internal IP, making it reachable only within the cluster.

💡 Hint

Think about whether the service is reachable from outside the cluster or only inside.

A ClusterIP service type creates an internal IP address that other pods inside the cluster can use to reach the service. It does not expose the service outside the cluster.

💻 Command Output

intermediate

What is the output of this command showing a ClusterIP service?

Given the command kubectl get svc my-service with this output, what is the ClusterIP address?

Kubernetes

NAME         TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
my-service   ClusterIP   10.96.123.45    <none>        80/TCP     5m

A 10.96.123.45

B my-service

C 80/TCP

D <none>

💡 Hint

Look for the column labeled 'CLUSTER-IP'.

The ClusterIP address is shown under the 'CLUSTER-IP' column. It is the internal IP used by other pods to access the service.

❓ Configuration

advanced

Identify the correct YAML snippet for a ClusterIP service

Which YAML snippet correctly defines a Kubernetes service of type ClusterIP exposing port 8080?

A

apiVersion: v1
kind: Service
metadata:
  name: my-service
spec:
  type: ClusterIP
  selector:
    app: my-app
  ports:
  - protocol: TCP
    port: 8080
    targetPort: 8080

B

apiVersion: v1
kind: Service
metadata:
  name: my-service
spec:
  type: LoadBalancer
  selector:
    app: my-app
  ports:
  - protocol: TCP
    port: 8080
    targetPort: 8080

C

apiVersion: v1
kind: Service
metadata:
  name: my-service
spec:
  type: NodePort
  selector:
    app: my-app
  ports:
  - protocol: TCP
    port: 8080
    targetPort: 8080

D

apiVersion: v1
kind: Service
metadata:
  name: my-service
spec:
  selector:
    app: my-app
  ports:
  - protocol: TCP
    port: 8080
    targetPort: 8080

💡 Hint

Check the type field for the service type.

Option A explicitly sets type: ClusterIP, which is the default and correct for a ClusterIP service. Option A omits the type, which defaults to ClusterIP but is less explicit. Options B and C specify other service types.

❓ Troubleshoot

advanced

Why can't pods outside the cluster access a ClusterIP service?

You created a ClusterIP service, but external clients cannot reach it. What is the reason?

A The service port is not open on the pod's container.

B The service selector labels do not match any pods.

C ClusterIP services are only accessible inside the cluster network, not from outside.

D The pod is not running.

💡 Hint

Think about the network scope of ClusterIP services.

ClusterIP services are designed to be reachable only within the cluster. External access requires other service types like NodePort or LoadBalancer.

✅ Best Practice

expert

Which practice ensures stable internal communication using ClusterIP services?

To maintain stable communication between pods using a ClusterIP service, what is the best practice?

A Expose the service as LoadBalancer for internal traffic.

B Use the service's DNS name instead of pod IPs directly.

C Use pod IP addresses directly for communication.

D Restart pods frequently to refresh connections.

💡 Hint

Consider what changes when pods restart or reschedule.

Pod IPs can change when pods restart, so using the service's DNS name (which points to the ClusterIP) ensures stable communication inside the cluster.