Why Ingress controllers (Nginx, Traefik) in Kubernetes? - Purpose & Use Cases

The Big Idea

What if one simple tool could handle all your app traffic without endless manual rules?

The Scenario

Imagine you have many websites and apps running on different servers. You want users to reach them all through one door, but you have to tell each server separately how to handle the traffic.

You write many rules manually for each server and update them every time something changes.

The Problem

This manual way is slow and confusing. If you forget to update a rule, users get errors or can't reach your apps.

It's hard to keep track of all the rules, and mistakes cause downtime or security risks.

The Solution

Ingress controllers like Nginx and Traefik act as smart traffic managers. They listen at one entry point and automatically send users to the right app based on simple rules.

They update themselves when you add or change apps, so you don't have to do it manually.

Before vs After

✗ Before

iptables -t nat -A PREROUTING -p tcp --dport 80 -j DNAT --to-destination 10.0.0.1:80
iptables -t nat -A PREROUTING -p tcp --dport 81 -j DNAT --to-destination 10.0.0.2:80

✓ After

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example-ingress
spec:
  rules:
  - host: app1.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: app1-service
            port:
              number: 80
  - host: app2.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: app2-service
            port:
              number: 80

What It Enables

With ingress controllers, you can easily manage many apps behind one address, making your system simpler and more reliable.

Real Life Example

A company runs multiple web apps for customers. Using Traefik, they route all traffic through one gateway, so customers access apps by friendly URLs without complex network setup.

Key Takeaways

Manual traffic routing is slow and error-prone.

Ingress controllers automate and simplify routing rules.

This leads to easier management and better user experience.

Practice

1. What is the main role of an Ingress controller like Nginx or Traefik in Kubernetes?

easy

A. To monitor pod resource usage

B. To manage Kubernetes cluster nodes

C. To store container images

D. To route external traffic to internal Kubernetes services

Solution

1. Step 1: Understand Ingress controller purpose

   Ingress controllers manage how external users access services inside the Kubernetes cluster.

2. Step 2: Identify correct function

   Nginx and Traefik route incoming traffic to the right service based on rules.

3. Final Answer:

   To route external traffic to internal Kubernetes services -> Option D

4. Quick Check:

   Ingress controller = traffic router [OK]

Hint: Ingress controllers route external traffic inside Kubernetes [OK]

Common Mistakes:

• Confusing ingress controller with node management
• Thinking ingress stores images
• Mixing ingress with monitoring tools

2. Which annotation correctly specifies the use of the Nginx ingress controller in a Kubernetes Ingress resource?

easy

A. kubernetes.io/ingress.class: "nginx"

B. ingress.kubernetes.io/controller: "traefik"

C. kubernetes.io/controller: "nginx"

D. ingress.class: "nginx-controller"

Solution

1. Step 1: Recall correct annotation key for ingress class

   The standard annotation to specify ingress controller is kubernetes.io/ingress.class.

2. Step 2: Match correct value for Nginx

   The value for Nginx ingress controller is "nginx".

3. Final Answer:

   kubernetes.io/ingress.class: "nginx" -> Option A

4. Quick Check:

   Annotation key = kubernetes.io/ingress.class [OK]

Hint: Use kubernetes.io/ingress.class: "nginx" for Nginx [OK]

Common Mistakes:

• Using wrong annotation keys
• Mixing Traefik and Nginx values
• Omitting quotes around values

3. Given this Ingress YAML snippet using Traefik:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example-ingress
  annotations:
    kubernetes.io/ingress.class: "traefik"
spec:
  rules:
  - host: example.com
    http:
      paths:
      - path: /app
        pathType: Prefix
        backend:
          service:
            name: app-service
            port:
              number: 80

What happens when a user visits http://example.com/app/page?

medium

A. Traffic goes to default backend ignoring /app path

B. Traffic is blocked because pathType is incorrect

C. Traffic is routed to the app-service on port 80

D. Ingress controller returns 404 error

Solution

1. Step 1: Analyze ingress rule for host and path

   The rule matches host example.com and path prefix /app, so /app/page matches.

2. Step 2: Check backend service and port

   Requests matching the path are sent to app-service on port 80.

3. Final Answer:

   Traffic is routed to the app-service on port 80 -> Option C

4. Quick Check:

   Path prefix match routes traffic correctly [OK]

Hint: Path prefix routes all subpaths to backend service [OK]

Common Mistakes:

• Assuming pathType Prefix is invalid
• Ignoring host match requirement
• Thinking default backend handles matched paths

4. You deployed an Nginx ingress controller but your Ingress resource is not routing traffic. Which fix is most likely correct?

medium

A. Add annotation kubernetes.io/ingress.class: "nginx" to the Ingress resource

B. Change service port to 8080 in the Ingress backend

C. Remove all annotations from the Ingress resource

D. Restart the Kubernetes API server

Solution

1. Step 1: Identify cause of routing failure

   Ingress controller routes traffic only to Ingress resources with matching ingress.class annotation.

2. Step 2: Apply correct annotation for Nginx

   Adding kubernetes.io/ingress.class: "nginx" tells Nginx controller to manage this Ingress.

3. Final Answer:

   Add annotation kubernetes.io/ingress.class: "nginx" to the Ingress resource -> Option A

4. Quick Check:

   Ingress class annotation enables controller routing [OK]

Hint: Add ingress.class annotation matching controller [OK]

Common Mistakes:

• Changing service port without checking actual port
• Removing annotations disables routing
• Restarting API server does not fix ingress routing

5. You want to expose two services, webapp and api, on the same domain using Traefik ingress. The webapp should respond on / and api on /api. Which Ingress configuration correctly achieves this?

hard

A. Create two Ingresses with same host but no annotations

B. Use one Ingress with two paths: / to webapp and /api to api service, with annotation kubernetes.io/ingress.class: "traefik"

C. Use one Ingress with only /api path to api service, and no path for webapp

D. Create one Ingress with annotation kubernetes.io/ingress.class: "nginx" for Traefik

Solution

1. Step 1: Understand routing requirements

   Both services share the same domain; webapp on root path /, api on /api path.

2. Step 2: Configure single Ingress with multiple paths and correct annotation

   One Ingress resource with two paths and annotation kubernetes.io/ingress.class: "traefik" directs traffic properly.

3. Final Answer:

   Use one Ingress with two paths: / to webapp and /api to api service, with annotation kubernetes.io/ingress.class: "traefik" -> Option B

4. Quick Check:

   Multiple paths in one Ingress with correct class [OK]

Hint: One Ingress, multiple paths, correct ingress.class annotation [OK]

Common Mistakes:

• Using wrong ingress.class annotation for Traefik
• Creating multiple Ingresses without annotations
• Missing path for root service