sig-release VS keptn

As Wednesday kicked off, it was great to feel the buzz and excitement of folks so eager to learn and connect. From Day 1’s keynote, I really enjoyed the reminder that companies benefiting from Kubernetes and the CNCF ecosystem should be getting involved, giving back, and mentoring others. There was a lot of love to maintainers and contributors in the ecosystem, and as someone involved in the Kubernetes Release Team for Kubernetes v1.25 and v1.26, it was a huge honor to see my face up in there with the rest of the team! 💙

Shout out to the SIG Release team once again for all of their hard work to ship 1.23. Release management is hard and often thankless work, and I appreciate their efforts so much. Also, I want to give a big thank you to everyone who contributed to 1.23. When I see such a long list of changes, it’s clear that many people worked hard to get them done.

Today the 1.22 version of Kubernetes ships. As always, hats off to the members of SIG Release for all of their hard work.

Here you go. https://github.com/kubernetes/sig-release/discussions/1877

One of the other places I spent a lot of time at at KubeCon NA was the CNCF Project Pavillion. I was very happy to see that it was a bit larger than the area we had during KubeCon EU, but I still wish that it was bigger and wasn’t so tucked away in the corner. A number of booths were showcasing their projects with demos through the week, hosted Q&A time, and gave away swag. If you are still trying to understand the Cloud Native Ecosystem, you can look at this very extensive map of the landscape and projects under the CNCF, some of which are more advanced than others. Of course I’m biased, but I’m really excited for the work that Keptn is doing in helping developers have more control over their application lifecycle. I’m also very excited to see where Backstage goes and how other CNCF projects can integrate with their service catalog.

I can’t speak from experience, but I think Keptn might be worth looking into: https://keptn.sh/

Go try this out and share your feedback on what you like about this integration and what you’d like improved. Feel free to create issues, engage in discussions on the Keptn Slack and Litmus Github repository. Stay tuned for more updates on how you can leverage Keptn & LitmusChaos CNCF projects to build and ship resilient cloud-native applications!

If you want, you can also manually download the binary file from Github and install the CLI by moving it into your path.