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.