← Problem Library
K8s L4 K8S 009 · 24 min

Only certain APIs return 404 due to an Ingress path-rewrite rule mismatch

Covers a path-rewrite problem where health checks pass but only real user requests fail.

K8sPlatform ReliabilityLevel 4Pro24 min
Scenario

A scenario that narrows down the root cause, centered on finding where the Ingress, Service, and application routing rules have drifted, in the situation of only certain APIs returning 404 due to an Ingress path-rewrite rule mismatch.

What to check first
  • Identify the primary failure signal in the Ingress Routing 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

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.

Questions worth viewing together
Why do only some API paths break in rewrite incidents?

The ingress path transform can be wrong for one route segment while the rest of the host still maps correctly.