Scenario
An observability stack is exposed through ingress and later only dashboard logins bounce in circles after an ingress tuning change.
An OpenSearch cluster behind Kubernetes ingress looks healthy and still drops...
The service is up, yet one login sequence loops because the two cookies control stickiness and auth on different path assumptions.
What to check first
- Identify the primary failure signal in the The Edge Session and the App Session Drew Different Cookie Boundaries 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 cookie path and domain scope across ingress and app session layers before rotating auth settings.
Questions worth viewing together
Community-field Kubernetes problem inspired by OpenSearch and Kubernetes community patterns where ingress affinity cookies conflicted with dashboard ses... Session loops can come from two valid cookies that disagree on routing and auth boundaries.
Teams often blame the security plugin when the ingress affinity cookie is the thing steering users inconsistently.
Cookie-based stickiness and cookie-based auth need joint scope review when apps sit behind ingress.
Similar cases seen in the field