🎯 What It Is

An Ingress is a Kubernetes resource that manages external HTTP/S access to services in your cluster — typically via hostnames, paths, and TLS.

✅ Without Ingress: You’d need NodePort or LoadBalancer for every service.

🔒 With Ingress: One entry point routes traffic to many services.

💡 Real-World Analogy

Like a reception desk in an office building:

• Visitor says: “I’m here for marketing” → sent to floor 3
• Visitor says: “I’m here for engineering” → sent to floor 5
• The building has one front door (Ingress), but many internal offices (Services)

🧪 Example: Expose Two Apps via One Ingress

Assume you have:

• A web Service (app: web)
• An api Service (app: api)

Step 1: Create an Ingress Resource

# ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
meta
  name: main-ingress
  namespace: default
spec:
  rules:
  - host: web.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: web
            port:
              number: 80

  - host: api.example.com
    http:
      paths:
      - path: /v1
        pathType: Prefix
        backend:
          service:
            name: api
            port:
              number: 80

Apply it:

kubectl apply -f ingress.yaml

✅ Result:

• http://web.example.com → web Service
• http://api.example.com/v1 → api Service

⚠️ But wait! This won’t work yet — you need an Ingress Controller (next topic).

✅ Summary YAML