A scenario that narrows down the root cause, centered on checking the policy difference between production traffic and health-check traffic, in the situation of only the load balancer health check being blocked by the firewall and dropping the whole service.
Only the load balancer health check is blocked by the firewall, dropping the whole service
A situation where the application is fine but a different health-check path policy drains all traffic.
Scenario
What to check first
- Identify the primary failure signal in the Firewall Policy scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- 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
If health checks are blocked, the load balancer can remove every backend even while direct node access still works.
Similar cases seen in the field