Hands-on Lab·Certified Kubernetes Administrator
Ingress Controllers
An Ingress is a request that some controller has to answer. Install ingress-nginx on bare metal, see what it actually is (a Deployment behind a NodePort), then create an Ingress naming a class nothing implements and watch it sit there doing nothing.
Services and Networking Guide 57 of 103 Intermediate
- Kubernetes1.36.4
- Cluster4 nodes
- Runtimecontainerd 2.2.6
- CNICalico v3.32.1
- TimeAbout 30 min
Node ports are allocated per install; yours will differ. The baremetal manifest is what avoids needing a LoadBalancer.
- ingress-nginxcontroller-v1.13.1
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA1001 | 192.168.0.175 | Ubuntu 26.04 LTS | Control Plane Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE01 | 192.168.0.176 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE02 | 192.168.0.177 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE03 | 192.168.0.178 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
This guide includes
Use this when an Ingress exists and nothing routes. This matters because Ingress is the one core Kubernetes API with no built-in implementation - an empty cluster accepts the object happily and then simply never answers it.
- finding what the controller actually is - a Pod and a Service, not part of Kubernetes itself
- standing up two identifiable backends so routing can be proven rather than assumed
- creating an Ingress that no controller claims, and reading the empty ADDRESS that says so
Before you start
- The Services guide, particularly why a LoadBalancer stays Pending on bare metal.
- A cluster where you can install a controller into its own namespace.
- The EndpointSlices guide, since an Ingress ultimately routes to Service endpoints.
-
What the controller actually is
-
Two backends, each identifiable
-
An Ingress nothing claims