Scenario
Host-network ingress remains ready while user traffic fails after firewall automation changed.
A host-network ingress stays ready and still fails traffic because firewall sync prunes the data port and leaves the health port alone
The probe path survives, but the real serving port is removed on one class of nodes.
What to check first
- Identify the primary failure signal in the The Probe Survived and the Real Port Disappeared 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
Compare probe and data-plane ports before blaming Services.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field