Why Ingress manages external access in Kubernetes - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary role of an Ingress in Kubernetes?

In Kubernetes, what main function does an Ingress resource serve?

A It controls external access to services inside the cluster, often via HTTP/HTTPS routing.

B It schedules pods onto nodes based on resource availability.

C It stores persistent data for stateful applications.

D It manages internal pod-to-pod communication within the cluster.

💡 Hint

Think about how users outside the cluster reach applications running inside.

An Ingress manages external access by routing incoming traffic to services inside the cluster, typically handling HTTP and HTTPS requests.

💻 Command Output

intermediate

Output of kubectl get ingress command

What output do you expect from kubectl get ingress if an Ingress resource named web-ingress is correctly configured?

Kubernetes

kubectl get ingress

A

NAME          CLASS    HOSTS             ADDRESS        PORTS   AGE
web-ingress   <none>   example.com       192.168.1.10   80      5m

B

NAME          READY   STATUS    RESTARTS   AGE
web-ingress   1/1     Running   0          5m

C

NAME          TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
web-ingress   LoadBalancer 10.0.0.1        <pending>     80        5m

D

NAME          READY   UP-TO-DATE   AVAILABLE   AGE
web-ingress   3/3     3            3           5m

💡 Hint

Look for the output format that shows hosts, addresses, and ports related to Ingress.

The kubectl get ingress command lists Ingress resources with columns like NAME, CLASS, HOSTS, ADDRESS, PORTS, and AGE.

❓ Configuration

advanced

Correct Ingress YAML for routing traffic

Which Ingress YAML snippet correctly routes HTTP traffic from myapp.example.com to a service named myapp-service on port 80?

A

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: myapp-ingress
spec:
  host: myapp.example.com
  backend:
    serviceName: myapp-service
    servicePort: 80

B

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: myapp-ingress
spec:
  rules:
  - host: myapp.example.com
    http:
      paths:
      - path: /
        backend:
          serviceName: myapp-service
          servicePort: 80

C

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

D

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: myapp-ingress
spec:
  rules:
  - host: myapp.example.com
    http:
      paths:
      - path: /
        pathType: ImplementationSpecific
        backend:
          service:
            name: myapp-service
            port:
              number: 8080

💡 Hint

Check the correct indentation and field names for Ingress backend service and port.

Option C uses the correct API version and the proper nested structure for backend service name and port number with pathType 'Prefix'.

❓ Troubleshoot

advanced

Why is external traffic not reaching the service via Ingress?

You created an Ingress resource, but external HTTP requests to your domain are not reaching the service. Which is the most likely cause?

A The service has no selector labels matching any pods.

B The Ingress controller is not installed or running in the cluster.

C The pod containers are missing readiness probes.

D The cluster nodes do not have enough CPU resources.

💡 Hint

Ingress resources need a controller to act on them and route traffic.

Without an Ingress controller, the Ingress resource rules are not enforced, so external traffic won't be routed to services.

✅ Best Practice

expert

Best practice for securing Ingress external access

Which practice best secures external access managed by an Ingress in Kubernetes?

A Use only HTTP protocol to reduce overhead and improve speed.

B Expose all services directly with NodePort to avoid Ingress complexity.

C Disable authentication on Ingress to simplify user access.

D Use TLS encryption with certificates and enforce HTTPS traffic in the Ingress rules.

💡 Hint

Think about protecting data in transit and user privacy.

Using TLS with HTTPS ensures encrypted communication, protecting data and user privacy when accessing services externally.