CNCF join status

[jkroepke]

Hi everyone,

we are currently exploring Kratix and see great potential for using it in our Internal Developer Platform.

In this context, I have two questions:

Are there any plans for Kratix to join the CNCF or to align more closely with the CNCF?

How do you ensure that the open source version will remain available in the long term, independent of a single vendor, and not be discontinued?

Thank you in advance for your feedback!

[hatofmonkeys]

Thank you for your interest in Kratix and for your thoughtful questions.
First, the core of Kratix is and will remain open source, available on GitHub under the Apache 2.0 license. This ensures the project is freely accessible and mitigates risks around adoption.
Second, Syntasso, the company behind Kratix, is deeply engaged in the CNCF community. We are proud CNCF members, and our team includes two CNCF Ambassadors. We actively participate in initiatives such as KubeCon, the colocated Platform Engineering Day, and Kubernetes Community Days, where we contribute to advancing the ecosystem.
Finally, regarding CNCF alignment: we are contiunously considering applying for Kratix to enter the CNCF Sandbox. At this stage, Kratix is evolving rapidly, and we want to ensure we dedicate the right level of resources and support to the process when the timing is right.
We remain committed to transparency, community collaboration, and ensuring that Kratix continues to thrive as an open-source project for the long term.

[jkroepke]

Hey @hatofmonkeys

thanks for your words. Great to see that Syntasso is active and engaged in the CNCF community.

We are currently building an IDP, and I tried Kratix as a POC. The general architecture and idea look great, but I feel it is still too early to use in production.

Anyway, I still have some head-scratches about Syntasso’s open source strategy. Missing a changelog and versioned releases is a clear signal that the open source version should not be used in production.