Ingress vs LoadBalancer Service decision in Kubernetes - Quick Revision & Key Differences

Recall & Review

beginner

What is a LoadBalancer Service in Kubernetes?

A LoadBalancer Service exposes your application externally using a cloud provider's load balancer. It provides a single IP to access the service directly.

beginner

What is an Ingress in Kubernetes?

An Ingress manages external access to services in a cluster, usually HTTP/HTTPS. It routes traffic based on rules like host or path to different services.

intermediate

When should you choose a LoadBalancer Service over an Ingress?

Choose LoadBalancer when you need a simple, direct external IP per service or when your cloud provider supports it easily.

intermediate

What are the benefits of using Ingress over LoadBalancer Services?

Ingress allows routing multiple services through one external IP, supports SSL termination, and offers flexible traffic rules.

advanced

Can you use both Ingress and LoadBalancer Services together?

Yes, you can use LoadBalancer to expose the Ingress controller itself, which then routes traffic to internal services.

What does a LoadBalancer Service provide in Kubernetes?

A Routing rules for multiple services

B Automatic SSL certificate management

C Internal cluster DNS resolution

D A direct external IP to access a service

A LoadBalancer Service provides a direct external IP to access a specific service from outside the cluster.

Which Kubernetes resource is best for routing HTTP traffic to multiple services based on URL paths?

A Ingress

B ConfigMap

C NodePort Service

D LoadBalancer Service

Ingress is designed to route HTTP/HTTPS traffic to multiple services using rules like URL paths or hostnames.

What is a key advantage of using Ingress over multiple LoadBalancer Services?

A Each service gets its own external IP

B Requires no configuration

C Simplifies external IP management by using one IP

D Works only inside the cluster

Ingress uses a single external IP to route traffic to many services, reducing the number of IPs needed.

How does an Ingress controller relate to a LoadBalancer Service?

A Ingress controller is exposed via a LoadBalancer Service

B Ingress controller replaces LoadBalancer Service

C LoadBalancer Service is inside Ingress controller

D They are unrelated

Typically, the Ingress controller is exposed externally using a LoadBalancer Service to receive traffic.

Which scenario favors using a LoadBalancer Service instead of Ingress?

A Multiple services with complex routing

B Simple service needing direct external access

C SSL termination for many services

D Routing based on hostnames

LoadBalancer Service is best for simple cases where a single service needs direct external access.

Explain the main differences between Ingress and LoadBalancer Service in Kubernetes.

Think about how external traffic reaches your services.

Describe a situation where using an Ingress controller with a LoadBalancer Service makes sense.

Consider combining both for scalable external access.

Practice

1. Which Kubernetes service type should you choose if you want to expose a single application with its own external IP address?

easy

A. LoadBalancer Service

B. Ingress Controller

C. ClusterIP Service

D. NodePort Service

Solution

1. Step 1: Understand service types

   LoadBalancer Service exposes an app with its own external IP, making it directly accessible.

2. Step 2: Compare with Ingress

   Ingress routes multiple apps through one IP, so it's not for single app direct exposure.

3. Final Answer:

   LoadBalancer Service -> Option A

4. Quick Check:

   Single app direct IP = LoadBalancer Service [OK]

Hint: Single app direct IP? Use LoadBalancer Service [OK]

Common Mistakes:

• Confusing Ingress with LoadBalancer for single app
• Choosing ClusterIP which is internal only
• Selecting NodePort which exposes on node ports, not external IP

2. Which of the following is the correct way to define a LoadBalancer service in a Kubernetes YAML manifest?

easy

A. apiVersion: networking.k8s.io/v1\nkind: LoadBalancer\nmetadata:\n name: my-service\nspec:\n selector:\n app: my-app\n ports:\n - protocol: TCP\n port: 80\n targetPort: 8080

B. apiVersion: v1\nkind: Service\nmetadata:\n name: my-service\nspec:\n type: Ingress\n selector:\n app: my-app\n ports:\n - protocol: TCP\n port: 80\n targetPort: 8080

C. apiVersion: v1\nkind: Service\nmetadata:\n name: my-service\nspec:\n type: NodePort\n selector:\n app: my-app\n ports:\n - protocol: TCP\n port: 80\n targetPort: 8080

D. apiVersion: v1\nkind: Service\nmetadata:\n name: my-service\nspec:\n type: LoadBalancer\n selector:\n app: my-app\n ports:\n - protocol: TCP\n port: 80\n targetPort: 8080

Solution

1. Step 1: Check apiVersion and kind

   Service resources use apiVersion: v1 and kind: Service.

2. Step 2: Confirm service type

   LoadBalancer type is set under spec.type to expose external IP.

3. Final Answer:

   YAML with kind Service and type LoadBalancer -> Option D

4. Quick Check:

   LoadBalancer service YAML uses kind Service and type LoadBalancer [OK]

Hint: LoadBalancer service uses kind Service and type LoadBalancer [OK]

Common Mistakes:

• Using kind LoadBalancer instead of Service
• Setting type to Ingress which is invalid for Service
• Confusing NodePort with LoadBalancer

3. Given this scenario: You have two apps, app1 and app2, and want to expose both externally using one IP with different paths. Which Kubernetes resource will handle this correctly?

medium

A. Two LoadBalancer Services, one for each app

B. One Ingress resource with path rules for app1 and app2

C. Two NodePort Services with different ports

D. One ClusterIP Service with multiple selectors

Solution

1. Step 1: Understand routing multiple apps on one IP

   Ingress allows routing multiple apps through one IP using path or hostname rules.

2. Step 2: Compare with LoadBalancer and others

   LoadBalancer exposes one app per IP; NodePort uses node ports, not one IP; ClusterIP is internal only.

3. Final Answer:

   One Ingress resource with path rules -> Option B

4. Quick Check:

   Multiple apps, one IP = Ingress with path rules [OK]

Hint: Multiple apps, one IP? Use Ingress with paths [OK]

Common Mistakes:

• Using multiple LoadBalancers wasting IPs
• Choosing NodePort which needs manual port management
• Thinking ClusterIP exposes externally

4. You created a LoadBalancer service but it never gets an external IP assigned. What is the most likely cause?

medium

A. You forgot to set spec.type to ClusterIP

B. Ingress controller is missing

C. Your Kubernetes cluster is running on a platform without LoadBalancer support

D. You used NodePort instead of LoadBalancer

Solution

1. Step 1: Check platform support for LoadBalancer

   Some clusters (like bare metal) do not support automatic external IP assignment for LoadBalancer services.

2. Step 2: Verify service type and controller

   Spec.type must be LoadBalancer, not ClusterIP; Ingress controller is unrelated; NodePort is different service type.

3. Final Answer:

   Platform lacks LoadBalancer support -> Option C

4. Quick Check:

   No external IP = platform lacks LoadBalancer support [OK]

Hint: No external IP? Check platform LoadBalancer support [OK]

Common Mistakes:

• Confusing ClusterIP with LoadBalancer type
• Assuming Ingress controller assigns LoadBalancer IP
• Mixing NodePort with LoadBalancer service

5. You want to minimize cloud costs while exposing 5 different apps externally. Which approach is best?

hard

A. Use one Ingress resource to route all 5 apps through a single LoadBalancer IP

B. Use ClusterIP services and expose each with a separate external IP

C. Use 5 NodePort services and expose nodes directly

D. Create 5 LoadBalancer services, one per app

Solution

1. Step 1: Understand cost implications of LoadBalancer IPs

   Each LoadBalancer service usually gets a separate external IP, increasing cloud costs.

2. Step 2: Use Ingress for cost efficiency

   Ingress lets multiple apps share one external IP with routing rules, saving costs.

3. Final Answer:

   One Ingress resource with single LoadBalancer IP -> Option A

4. Quick Check:

   Multiple apps, minimize cost = Ingress with one LoadBalancer IP [OK]

Hint: Multiple apps, one IP saves cost: use Ingress [OK]

Common Mistakes:

• Creating multiple LoadBalancers wasting IPs and money
• Using NodePort exposes nodes, less secure and complex
• ClusterIP cannot expose apps externally