Ingress resource definition in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of kubectl get ingress command

Given this Ingress YAML, what will be the output of kubectl get ingress my-ingress?

Kubernetes

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

A

NAME         CLASS    HOSTS         ADDRESS   PORTS   AGE
my-ingress   <none>   example.com   <none>   80      1m

B

NAME         HOSTS         ADDRESS   PORTS   AGE
my-ingress   example.com             80      1m

C

NAME         CLASS    HOSTS         ADDRESS   PORTS   AGE
my-ingress   <none>   example.com             80      1m

D

NAME         CLASS    HOSTS         ADDRESS   PORTS   AGE
my-ingress   <none>   example.com             443     1m

💡 Hint

Look carefully at the columns shown by kubectl get ingress and the ports defined.

The default output of 'kubectl get ingress' includes columns NAME, CLASS, HOSTS, ADDRESS, PORTS, and AGE. Since the Ingress defines port 80, PORTS shows 80. CLASS is usually if no ingressClass is specified.

❓ Configuration

intermediate

Correct Ingress pathType usage

Which Ingress resource snippet correctly uses pathType to match all paths starting with /api?

A

paths:
- path: /api
  pathType: Prefix
  backend:
    service:
      name: api-service
      port:
        number: 8080

B

paths:
- path: /api*
  pathType: Prefix
  backend:
    service:
      name: api-service
      port:
        number: 8080

C

paths:
- path: /api/
  pathType: ImplementationSpecific
  backend:
    service:
      name: api-service
      port:
        number: 8080

D

paths:
- path: /api
  pathType: Exact
  backend:
    service:
      name: api-service
      port:
        number: 8080

💡 Hint

Prefix matches all paths starting with the given prefix exactly as written.

Using pathType: Prefix with path /api matches all requests starting with /api, such as /api/users. Exact matches only /api exactly. ImplementationSpecific behavior varies by ingress controller. Using wildcards like * in path is invalid.

❓ Troubleshoot

advanced

Ingress not routing to service

You created this Ingress but requests to http://example.com/app return 404. What is the most likely cause?

Kubernetes

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

A The service name app-service is incorrect and does not exist in the cluster.

B The pathType Exact requires the request path to be exactly /app, but the request URL has a trailing slash or extra path segments.

C The Ingress resource is missing the ingressClassName field.

D The Ingress resource must specify the port name instead of port number.

💡 Hint

Check how pathType Exact matches request paths.

pathType Exact matches only the exact path /app. Requests like /app/ or /app/page will not match and return 404. Using pathType Prefix would match all paths starting with /app.

🧠 Conceptual

advanced

Understanding Ingress TLS configuration

Which statement about TLS configuration in a Kubernetes Ingress resource is correct?

A TLS configuration in Ingress automatically redirects HTTP traffic to HTTPS.

B TLS configuration is optional and ignored if no hosts are specified in the TLS section.

C The TLS secret must contain only the private key, the certificate is fetched automatically from the cluster.

D The TLS section specifies the secret name containing the TLS certificate and the hosts it applies to.

💡 Hint

Think about what the TLS section defines and what it requires.

The TLS section in an Ingress specifies the secret holding the TLS certificate and private key, and the hosts for which TLS applies. It does not automatically redirect HTTP to HTTPS; that requires additional configuration.

✅ Best Practice

expert

Best practice for Ingress resource annotations

Which annotation is recommended to enable automatic HTTPS redirect in NGINX Ingress Controller?

A nginx.ingress.kubernetes.io/ssl-redirect: "true"

B nginx.ingress.kubernetes.io/force-ssl-redirect: "false"

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

D nginx.ingress.kubernetes.io/use-regex: "true"

💡 Hint

Look for the annotation that controls SSL redirect behavior.

The annotation 'nginx.ingress.kubernetes.io/ssl-redirect: "true"' enables automatic redirect from HTTP to HTTPS in the NGINX Ingress Controller. Other annotations control different behaviors.