LoadBalancer service type in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the LoadBalancer service type in Kubernetes?

It exposes the service externally using a cloud provider's load balancer, distributing traffic to the service pods.

beginner

How does a LoadBalancer service type differ from a ClusterIP service type?

ClusterIP exposes the service only inside the cluster, while LoadBalancer exposes it externally with a cloud load balancer.

intermediate

Which cloud providers support the LoadBalancer service type in Kubernetes by default?

Popular cloud providers like AWS, GCP, and Azure support LoadBalancer service type by provisioning external load balancers automatically.

intermediate

What happens when you create a LoadBalancer service in a Kubernetes cluster without cloud provider integration?

The service will be created but no external load balancer will be provisioned, so it won't be accessible outside the cluster.

beginner

What key field must be set in a Kubernetes service manifest to create a LoadBalancer service?

The field 'spec.type' must be set to 'LoadBalancer' in the service manifest.

What does the LoadBalancer service type do in Kubernetes?

A Exposes the service externally using a cloud load balancer

B Exposes the service only inside the cluster

C Creates a DNS record for the service

D Scales the number of pods automatically

LoadBalancer service type creates an external load balancer to expose the service outside the cluster.

Which field in the service manifest defines the LoadBalancer type?

A spec.type

B spec.selector

C metadata.name

D spec.ports

The 'spec.type' field must be set to 'LoadBalancer' to create a LoadBalancer service.

If your Kubernetes cluster is not on a cloud provider, what happens when you create a LoadBalancer service?

A The service is exposed via NodePort

B An external load balancer is created automatically

C The service fails to create

D The service is only accessible inside the cluster

Without cloud provider integration, no external load balancer is created, so the service is only accessible inside the cluster.

Which cloud providers commonly support Kubernetes LoadBalancer services?

A All on-premise clusters

B DigitalOcean only

C AWS, GCP, Azure

D Local Minikube clusters

AWS, Google Cloud Platform, and Azure provide native support for LoadBalancer services.

What is the main benefit of using a LoadBalancer service type?

A Automatic pod scaling

B Automatic external access with load balancing

C Faster pod startup times

D Internal DNS resolution

LoadBalancer service type provides automatic external access and distributes traffic across pods.

Explain how the LoadBalancer service type works in Kubernetes and when you would use it.

Think about how users outside the cluster reach your app.

Describe the difference between ClusterIP, NodePort, and LoadBalancer service types in Kubernetes.

Consider where the service is accessible from.

Practice

1. What does the LoadBalancer service type do in Kubernetes?

easy

A. It creates multiple internal IPs for the service.

B. It only exposes the service inside the cluster without external access.

C. It exposes the service externally with a cloud provider's load balancer and a single external IP.

D. It automatically scales the number of pods based on load.

Solution

1. Step 1: Understand LoadBalancer service purpose

   The LoadBalancer service type is designed to expose a Kubernetes service externally using a cloud provider's load balancer.

2. Step 2: Identify the external IP behavior

   It provides a single external IP address that routes traffic to the service pods.

3. Final Answer:

   It exposes the service externally with a cloud provider's load balancer and a single external IP. -> Option C

4. Quick Check:

   LoadBalancer = external IP + cloud load balancer [OK]

Hint: LoadBalancer = external IP + cloud load balancer [OK]

Common Mistakes:

• Confusing LoadBalancer with ClusterIP (internal only)
• Thinking it creates multiple external IPs
• Assuming it auto-scales pods

2. Which of the following is the correct YAML snippet to create a LoadBalancer service in Kubernetes?

easy

A. apiVersion: v1
kind: Service
metadata:
name: my-service
spec:
type: NodePort
ports:
- port: 80
selector:
app: my-app

B. apiVersion: v1
kind: Service
metadata:
name: my-service
spec:
type: ExternalName
ports:
- port: 80
selector:
app: my-app

C. apiVersion: v1
kind: Pod
metadata:
name: my-service
spec:
type: LoadBalancer
ports:
- port: 80
selector:
app: my-app

D. apiVersion: v1
kind: Service
metadata:
name: my-service
spec:
type: LoadBalancer
ports:
- port: 80
selector:
app: my-app

Solution

1. Step 1: Identify correct kind and type

   The resource must be kind: Service and spec.type: LoadBalancer to create a LoadBalancer service.

2. Step 2: Check YAML correctness

   apiVersion: v1 kind: Service metadata: name: my-service spec: type: LoadBalancer ports: - port: 80 selector: app: my-app correctly uses kind: Service and type: LoadBalancer with proper ports and selector.

3. Final Answer:

   YAML with kind: Service and type: LoadBalancer -> Option D

4. Quick Check:

   LoadBalancer service YAML uses kind: Service + type: LoadBalancer [OK]

Hint: LoadBalancer service YAML: kind Service + type LoadBalancer [OK]

Common Mistakes:

• Using kind: Pod instead of Service
• Using wrong service type like NodePort or ExternalName
• Missing selector or ports section

3. Given this service YAML with type LoadBalancer, what will kubectl get svc my-service show for the EXTERNAL-IP field after creation?

apiVersion: v1
kind: Service
metadata:
  name: my-service
spec:
  type: LoadBalancer
  ports:
  - port: 80
  selector:
    app: my-app

medium

A. An external IP address like 34.68.123.45

B. <none>

C. Pending

D. ClusterIP address like 10.0.0.1

Solution

1. Step 1: Understand LoadBalancer external IP assignment

   When a LoadBalancer service is created, the cloud provider assigns an external IP address to the service, visible in EXTERNAL-IP field.

2. Step 2: Recognize typical EXTERNAL-IP values

   Initially, EXTERNAL-IP may show Pending, but after provisioning, it shows an actual external IP like 34.68.123.45.

3. Final Answer:

   An external IP address like 34.68.123.45 -> Option A

4. Quick Check:

   LoadBalancer EXTERNAL-IP = cloud IP address [OK]

Hint: LoadBalancer EXTERNAL-IP shows cloud IP, not ClusterIP [OK]

Common Mistakes:

• Expecting <none> or ClusterIP in EXTERNAL-IP field
• Confusing Pending state as final
• Thinking LoadBalancer does not assign external IP

4. You created a LoadBalancer service but kubectl get svc shows EXTERNAL-IP as "Pending" indefinitely. What is the most likely cause?

medium

A. The Kubernetes cluster is not running on a cloud provider that supports LoadBalancer.

B. The service selector does not match any pods.

C. The service type is incorrectly set to ClusterIP.

D. The pod containers do not expose the correct port.

Solution

1. Step 1: Understand LoadBalancer external IP provisioning

   LoadBalancer service requires cloud provider support to provision an external IP and load balancer.

2. Step 2: Identify cause of Pending EXTERNAL-IP

   If the cluster runs on bare metal or unsupported environment, the external IP stays Pending indefinitely.

3. Final Answer:

   The Kubernetes cluster is not running on a cloud provider that supports LoadBalancer. -> Option A

4. Quick Check:

   Pending EXTERNAL-IP means no cloud LB support [OK]

Hint: Pending EXTERNAL-IP means no cloud load balancer support [OK]

Common Mistakes:

• Blaming pod selector or ports for EXTERNAL-IP Pending
• Confusing service type ClusterIP with LoadBalancer
• Ignoring cluster environment limitations

5. You want to expose a Kubernetes app externally with a LoadBalancer service, but your cluster runs on bare metal without cloud support. Which approach will work best?

hard

A. Use ClusterIP service type and access pods internally only.

B. Change service type to NodePort and use external node IP with the node port.

C. Use LoadBalancer service type and wait for external IP assignment.

D. Delete the service and expose pods directly with hostPort.

Solution

1. Step 1: Recognize LoadBalancer limitation on bare metal

   LoadBalancer service requires cloud provider support, which bare metal lacks, so it won't get an external IP.

2. Step 2: Choose alternative external exposure method

   NodePort exposes the service on each node's IP at a static port, allowing external access without cloud load balancer.

3. Final Answer:

   Change service type to NodePort and use external node IP with the node port. -> Option B

4. Quick Check:

   Bare metal + external access = NodePort service [OK]

Hint: Bare metal clusters use NodePort for external access, not LoadBalancer [OK]

Common Mistakes:

• Expecting LoadBalancer to work without cloud support
• Using ClusterIP which is internal only
• Exposing pods directly with hostPort is less flexible