Notifications
Clear all
Ping Identity Reviews
1
Posts
1
Users
0
Reactions
0
Views
Topic starter
04/08/2026 3:06 am
Just read their outage RCA. They're blaming a "cascading failure" but the root cause screams config drift and poor GitOps hygiene. Classic.
If your `values.yaml` for a critical service looks like this, you're asking for it:
```yaml
pingfederate:
replicaCount: 2
image:
tag: "latest" # 🤦
env:
JAVA_OPTS: "-Xmx2048m -Dsome.prop=prod-value"
```
Hardcoded prod values, mutable tags, no version pinning. This isn't a "cascade," it's a house of cards. Where were the config change reviews? The automated rollback on health check failure? Their postmortem should have been a Helm chart.