A Kubernetes Ingress declaratively defines how traffic entering a cluster from external clients reaches services inside it. It provides a controlled entry point instead of exposing each service independently. section 2.1.2 section 2.3.6
Use an Ingress to:
- Route requests through a single entry point. section 2.3.6
- Apply path-based routing to direct traffic to different services. section 2.3.6
- Reference service names rather than container IP addresses. section 2.3.6
- Keep routing rules simple; business logic does not belong at this layer. section 2.3.6
Inspecting the frontend Ingress
Run `kubectl get ingress` to list resources, then `kubectl describe ingress conference-frontend-ingress` to inspect its controller, host, path, backend, address, and events. A representative rule routes `/` to the `frontend` service on port 80, which forwards to the application’s container endpoints. section 2.3.6
Listing 2.8 Describing the Ingress resource
Name: conference-frontend-ingress
Labels: app.kubernetes.io/managed-by=Helm
Namespace: default
Address: localhost
Ingress Class: nginx
Default backend: <default>
Rules:
Host Path Backends
---- ---- --------
*
/ frontend:80 (10.244.1.6:8080,10.244.2.9:8080) #1
Annotations: meta.helm.sh/release-name: conference
meta.helm.sh/release-namespace: default
nginx.ingress.kubernetes.io/rewrite-target: /
Events: <none>
Inspect the rendered Ingress details, including the nginx class, localhost address, root path, frontend backend, and rewrite annotation. section 2.3.6
