What does confidence in an upgrade look like? Seeing an upgrade applied? Seeing that something is running at the expected version? Or is it knowing that something is healthy following an upgrade? In the latest version of SKE, v0.63.0, we've introduced health-informed upgrades. Now, an upgrade only moves on when your Resource Requests pass their Health Checks.
We love GitOps.
Kratix, a framework for building platforms on top of Kubernetes, has GitOps at its core, and it's a fundamental part of our recommended platform architecture. It’s what allows Kratix to schedule workloads to any type of Destination, what enables Compound Promises, and a central piece of the declare-and-converge philosophy we follow.
But what happens when hundreds of commits are pushed in a short period? Or when customers want to know "who did that?", but the answer is buried under thousands of automated commits? Or even when you can't commit to the repository at all?
In this blog, we will cover how our health checks turned a GitOps repository into a commit firehose, why switching to buckets was not enough, and how the new Health Source in SKE puts the Platform back in control.
We at Syntasso are very proud of the SKE Backstage integration we built. You apply a Promise, and a Component and a Template automagically appear in your Backstage instance. You can send requests to the platform via GitOps or directly via the Kubernetes API. Changes to the Promise regenerate the Template. You can use an array of CRD properties to control the validation applied to the form, and you can run custom containers to customise what the platform generates.
It is great.
Except, it kinda looks like this:
Which is enough to get you started, but it won't necessarily wow the platform users. It solved the immediate problem for the platform engineer (how do I expose this service on Backstage?), but it was quite simple on the visual front. Apparently raw YAML is not everyone's cup of tea… not sure why. it better.
In this post, we will explore why the interface matters and how it can drive adoption of your platform. We'll look at what we had before, what we have learned from our customers, and how we used that learning to improve the out-of-the-box experience with Backstage. We will then look at what we have just released to make it even better.
Hi friends 😊 I'm Cat, Product Manager here at Syntasso, and I've been listening to you, our avid followers. "Cat, we love Kratix, and we love your team; we want an update!" I hear you scream, so here I am, delivering this top-quality content. You're welcome.
Given that this is our first Kratix Product Update™ (not really ™), I wanted to shout about some of the great work the team has done over the last few months, so we're going back a bit further than we usually will… Indulge me; it was my birthday this month.
If you only have 10 seconds spare to read this blog, these are the features you need to know about:
