Alex, Not only the images we should remove/deprecate as we did with Mongo etc. We also need to review the examples, docs, and so on. Including this: https://github.com/knative-extensions/eventing-kogito
I'll do a doc for this assessment later this week and share it with the community. A part from that, can I have more +1? :) Cheers! On Sun, Jan 28, 2024 at 10:53 AM Alex Porcelli <[email protected]> wrote: > Was thinking about this proposal and the potential additional impact. > > if we don’t ship operator, we may not need provide out of the box the > images, so less code and security surface to cover (ie. CVEs). > > I understand we’ll continue with the serverless workflow operator, so my > suggestion is reduce the images by the only ones used by serverless > workflow operator. > > > On Fri, Jan 26, 2024 at 2:08 PM Jason Porter <[email protected]> > wrote: > > > Do we have the minutes at least for this weekly meeting we can post on > the > > mailing list, or an accessible link at least? > > > > On 2024/01/26 15:05:26 ricardo zanini fernandes wrote: > > > 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. > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
