Hands-on Lab·Certified Kubernetes Administrator
Ingress Routing Rules
The obvious path-based Ingress returns 404, and the 404 comes from your application rather than the controller. The path is matched and then forwarded unchanged, so the backend is asked for a directory it does not have.
Services and Networking Guide 58 of 103 Intermediate
- Kubernetes1.36.4
- Cluster4 nodes
- Runtimecontainerd 2.2.6
- CNICalico v3.32.1
- TimeAbout 35 min
rewrite-target is an ingress-nginx annotation, not part of the Ingress API. Other controllers spell it differently.
- 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 a path-based Ingress returns 404 and you cannot tell who produced it. This matters because the obvious Ingress is wrong in a way that looks exactly like a controller bug, while the 404 is actually coming from your own application.
- writing the obvious two-path Ingress and getting a 404 back from it
- bypassing the Ingress to ask the backend directly, and getting the very same answer
- adding
rewrite-targetwith the capture group it needs to strip the prefix - matching on host as well as path, and seeing what a miss looks like
Before you start
- The Ingress controllers guide, which installs the controller and the two backends this one routes to.
- The Services guide.
- A shell with
curlthat can reach a node's HTTP node port.
-
The obvious version, and it returns 404
-
Ask the backend directly and the answer is the same
-
rewrite-target, and the capture group it needs
-
Host routing, and what a miss looks like