squakez opened a new pull request, #4025: URL: https://github.com/apache/camel-k/pull/4025
<!-- Description --> The goal of this PR is to collect early feedback. Ideally this one should be one of the first PR for Camel K 2.0 branch. It partially address the requirements expressed in #3831. The first goal is to make this mostly compatible with the design and the process in 1.x. We could even include it in any 1.x if we decide to. The main goal is to decouple the strong dependency we have from Camel K Runtime and the Mandrel container image which is required to build a Quarkus native application. With this PR we're making a CamelCatalog a dynamic CR which is in charge to build its own builder image with the required tools that will be eventually used in the `pod` strategy build. With this PR we'll be basically free to start our own release cadence, as Camel K should be able to run any Camel K Runtime. The only drawback is that we are forcing any Native build to be run in a `pod` strategy (which could even seen as a benefit, and maybe in the future as the default strategy to build). I've decomposed it in a series of commits which hopefully makes the PR easier to review. With 6932f1e1130c6eaa27274fdac194693cb91b53ed I am introducing the possibility to enable a `pod` strategy in the Builder trait. With this, the user can decide to spin off a build pod strategy without requiring to edit the IntegrationPlatform. With 5aba5a0871f7a94c866c6c7adb1683b0f164cc28 we force any Quarkus Native build to spin off a build strategy `pod`. This is required as the tools required by a native build are going to be moved off the container and included in a dynamic container builder image. With c49e257968ada0edd713011eca92d80f9f71e9b6 7dad4e1897a1712b08a5306d4a5d1652252a4d63 and 2b5fde826f521516ea16fdeb580981652df26eab I've removed the dependency from Maven favoring instead the presence of the Maven wrapper. With 0aee1a8791bf5c18cf72e338b3b816e4a79aa352 I'm introducing the concept of a builder image which is an image containing the tools required by a given catalog in order to run its build duties. This image is created on the fly on Camel Catalog reconcilation, which I introduced in 13d6fdc75c5515cceeaa0a92d761d915a656de87 The latest commits were polishing and optimizing the work done in the first iterations. <!-- Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required". If no release note is required, write "NONE". You can (optionally) mark this PR with labels "kind/bug" or "kind/feature" to make sure the text is added to the right section of the release notes. --> **Release Note** ```release-note feat: Free Camel K from runtime dependency ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
