I’m exploring whether this is a real problem: Kubernetes teams define resilience and SLO expectations, but often validate them only occasionally or reactively rather than proactively.
Do you validate these expectations before releases or continuously over time? Is this a real pain, already solved, or simply not a priority?
I’m exploring whether this is a real problem: Kubernetes teams define resilience and SLO expectations, but often validate them only occasionally or reactively rather than proactively.
Do you validate these expectations before releases or continuously over time? Is this a real pain, already solved, or simply not a priority?
I’ve put together a small site explaining the idea: https://www.resilopshq.com/
I’ve also built an MVP SaaS tool around this approach. If anyone is interested in trying it, I’d be happy to provide free early access.