Friends,

As discussed in the weekly meeting, I'm proposing to archive the legacy
Kogito Operator repository and not make it part of the next release.

Reasons are:

1. It uses a very old concept of deploying applications that today can be
achieved via Quarkus Addons and SpringBoot tools.
2. One can also use Helm Charts and pipelines tooling to do the same
3. It has the old `kogito cli` that lost traction. One can use kubectl or
quarkus cli to achieve the same
4. It deploys explainability, trusty, infinispan, and other services that
we are not supporting anymore.

I'll archive the repository and I can write a blog post about this decision
once we have a release.

I'll update the pipelines to not run it anymore too.

I need your +1 to move ahead.

Cheers!
--
Ricardo Zanini Fernandes
Vida longa e próspera.

Reply via email to