← Problem Library
K8s L5 K8S 1203 · 22 min

Ingress health looks good but one path still 404s because the rewrite logic diverges between edge and controller

The ingress resource looks healthy overall, yet one route returns 404 because the edge layer and ingress controller disagree about how the path should be rewritten.

K8sPlatform ReliabilityLevel 5Pro22 min
Scenario

A rewrite snippet copied from community answers works for one route. Another path still 404s because an upstream edge layer is also transforming the path unexpectedly.

What to check first
  • Identify the primary failure signal in the Rewrite Boundary Debug scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Compare edge rewrite behavior with controller rewrite behavior before blaming the backend routes.

Questions worth viewing together
What should you verify first when Ingress health looks good but one path still 404s appears?

Community-derived ingress 404 problem based on Stack Overflow and Reddit patterns where path rewrite logic diverged across layers. A healthy ingress object does not prove every path transformation is aligned end to end.

What usually causes Ingress health looks good but one path still 404s in production?

Teams often debug app routing when the transformed path is already wrong before the request arrives.

What should you document after resolving Ingress health looks good but one path still 404s?

Multiple rewrite-capable layers can make one healthy route hide another broken one.