squakez opened a new issue, #4648:
URL: https://github.com/apache/camel-k/issues/4648
This command is used by the Pod strategy in order to allow the build of the
maven application and the execution of the publishing strategy. However, this
bring in a circular reference problem and requires the creation of a dynamic
builder image in order to include the `kamel` binary into the builder Pod.
As in Camel K 2 we have the new concept of pipeline, we can split each task
and have it run by its specific image and get rid off the dynamic builder
image. Ideally we should have some Build configuration as:
```
tasks:
# Will take care to build a maven application as required by the runtime
- builder:
image: eclipse-temurin:17
...
# Optional, only when native build required - package as native
- native:
image:
quay.io/quarkus/ubi-quarkus-mandrel-builder-image:22.2.0.0-Final-java11
...
# Will take care to perform the push to the registry
- spectrum:
image: spectrum-image?
...
```
The above is a draft idea that can lead to some change in the design to be
further analyzed.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
