Hi folks, you may remember that in Camel K operator we used the Camel K Runtime java project [1] as a lightweight layer on top of Camel Quarkus as a runtime. Since last year, we have stopped upgrading the runtime project as we have moved directly to what we called "plain-quarkus" provider, which is running directly Camel Quarkus runtime. The old runtime is based on Quarkus 3.15 (Camel 4.8). I guess most of the users have moved already to the new runtime, so I propose to deprecate the runtime project [1] and archive it in a few months.
On the Camel K operator side so far we haven't moved the default to the newer "plain-quarkus" in order to avoid a breaking compatibility change. However we've invited since longer than a year (version 2.6.0) to move to the new runtime, so I was considering to introduce a breaking compatibility change in version 2.11.0 in order to default to the new runtime and let the user still use the older runtime at their discretion (although no longer supported). Of course we will document this in the release notes and provide backward compatibility configuration. I've never been very keen to do compatibility changes outside majors, but, given that the old runtime is not really supported and potential target of vulnerabilities that we won't fix on such old Camel versions, I think it's the safest path both for maintainers and for final users. Please, let me know your thoughts and above all if there is any objection to this plan. Cheers, Pasquale. [1] https://github.com/apache/camel-k-runtime
