New in Kratix: Health Checks and Progressive Rollout
Earlier this year, we introduced an exciting new capability in Kratix: health checks for resources. This addition allows platform teams and app developer to easily observe the status of their requested workloads, without the need to switch context and find it in Destinations.
In this blog, we’ll discuss how you can use it to support progressive rollouts when updating Promises.
What’s the Problem?
When a Promise gets updated, say with a new version of a Helm chart, the standard behavior in Kratix is to reconcile and update all resource requests at once. That’s fine in simple dev environments, but for complex workloads, upgrading everything at once is risky. A failed update could disrupt many environments simultaneously, and debugging becomes difficult when failures are scattered.
Platform engineers need a safer approach: progressive rollouts. Instead of deploying changes to your entire fleet at once, progressive rollout allows teams to introduce updates gradually to limit the impact, gather early feedback, and catch potential bugs before releasing broadly. But for that to work, Kratix needs a way to understand the health of each individual resource during and after an upgrade.