[Solved] You applied this Ingress YAML but traffic is not routing correctly: apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: bad-ingress spec: rules: - http: paths: - path: /app pathType:... | Kubernetes

Kubernetes - Ingress

You applied this Ingress YAML but traffic is not routing correctly:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: bad-ingress
spec:
  rules:
  - http:
      paths:
      - path: /app
        pathType: Prefix
        backend:
          serviceName: app-service
          servicePort: 80

What is the likely cause of the problem?

AMissing host field in rules

BIncorrect apiVersion for Ingress

CUsing deprecated backend syntax serviceName and servicePort instead of service.name and service.port.number

DMissing metadata name field

Step-by-Step Solution

Solution:

Step 1: Check backend syntax in Ingress spec
The YAML uses old syntax with serviceName and servicePort which is deprecated in networking.k8s.io/v1.
Step 2: Confirm correct syntax
Correct syntax uses service.name and service.port.number fields under backend.service.
Final Answer:
Using deprecated backend syntax serviceName and servicePort instead of service.name and service.port.number -> Option C
Quick Check:
Use service.name and service.port.number in Ingress backend [OK]

Quick Trick: Use service.name and service.port.number for backend in networking.k8s.io/v1 [OK]

Common Mistakes:

Using old backend syntax causing Ingress controller to ignore rules
Assuming missing host always breaks routing
Confusing apiVersion correctness
Forgetting metadata name

Master "Ingress" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More Kubernetes Quizzes

You applied this Ingress YAML but traffic is not routing correctly:

Step 1: Check backend syntax in Ingress spec

Step 2: Confirm correct syntax

Final Answer:

Quick Check:

Want More Practice?