Kogito Operator - Assessment for Archiving

[ricardozanini]

From this date onward, the ASF KIE Community has decided to archive the Kogito Operator project. No more updates, releases, and fixes. The repository will be archived for good.

This hurtful decision came after the recent migration to ASF and the repurposing of many projects under KIE. Most importantly, we understand that this operator doesn't add to the project or community anymore. What it does, can be accomplished easily using Quarkus, Helm, Tekton, or any other current image build tooling out there:

• Quarkus Guides - CONTAINER IMAGES
• SpringBoot Docs - Container Images
• Tekton - Getting Started
• ArgoCD - Getting Started
• OpenShift - Creating Images
• Kaniko Tutorial
• Helm Charts

This operator was capable of:

• Building and deploying Kogito applications (BPMN, DMN, Drools). That can be accomplished via Quarkus or SpringBoot container libraries. In the cluster, you can use Tekton or if using OpenShift, rely on their multiple ways of deploying images.
• Deploying Kogito Supporting Services. Via the images we already publish, you can deploy them using ArgoCD and Helm using the GitOps approach.

Impact Assessment

Having the Kogito Operator archived, would impact the following repositories:

• Kogito Examples: A few examples have an operator folder that contains CRDs from this operator
• KIE Docs: There's an entire section dedicated to the operator and other sections mentioning it
• Kogito Images: This repo is responsible for maintaining all the images managed by this operator. Those images will also be deprecated and removed from the repository
  • kogito-base-builder
  • kogito-runtime-jvm
  • kogito-runtime-native
  • kogito-s2i-builder
• Kogito Pipelines: To disable and remove Kogito Operator pipelines from ASF infrastructure

Under Review

A few images are also deployed with Kogito Operator, but may be supported by the community going further:

• kogito-task-console
• kogito-management-console