Kamaji restrictions and Cozystack?

[nwmcsween]

Kamaji is effectively subscription based except for unstable releases, is there an alternative cozystack has looked into?

[gecube]

@nwmcsween Hi! It is really great that you raised this issue. What are your worries? Kamaji shown that it's "unstable" release is more stable than some competitors.

[nwmcsween]

Because it's a risk, no production environment will really want to use something that is labeled unstable

[kvaps]

We are familiar with codebase and do testing for every release update.
We already build our own images as part of platform, want to add more integration tests, so I think this should not be an issue.

Cozystack includes many things which are alpha for now, but we perform testing to ensure that all the required functions are working as expected.

We're not going to replace Kamaji to something else for now

[kvaps]

Because it's a risk, no production environment will really want to use something that is labeled unstable

In our case we use kamaji just like a tool for spawning Kubernetes control-planes in limited configuration. This can be covered with tests very quickly.

As an alternative we want to provide the functionality to every vendor solution we use to provide their own production-ready images. We already have this oportunity for FluxCD, we can enable this for Kamaji as well.

Would you be interested in that?

/cc @prometherion may be you can comment on this

[nwmcsween]

No problem just wanted to know if replacing kamaji was on the table or if the "unstable" public releases were an issue for adoption.

…

On Tue, Sep 24, 2024, 11:40 PM Andrei Kvapil ***@***.***> wrote: We are familiar with codebase and do testing for every release update. We already build our own images as part of platform, want to add more integration tests, so I think this should not be an issue. Cozystack includes many things which are alpha for now, but we perform testing to ensure that all the required functions are working as expected. We're not going to replace Kamaji to something else for now — Reply to this email directly, view it on GitHub <#354 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEYC36O43NZJJ2BMK4FPZ3ZYJLEJAVCNFSM6AAAAABOXLKS2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZTGE3DCNBWHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[prometherion]

The first thing here would be defining the term "stable": did you notice something broken in Kamaji itself, or a misbehavior of the Operator?

We do our best in pushing changes that are production grade and non breaking, as well as running e2e at every commit: CLASTIX directly cut offs stable versions from the upstream and our customers are happy for this approach and see value in our work.