squakez opened a new issue, #5588: URL: https://github.com/apache/camel-k/issues/5588
### Requirement This issue is collecting some possible idea around the feature discussed in this chat [1]. The requirement has been popping in several occasions, so I think it deserve some space to be officially discussed with any possible pro and cons. I was thinking that, with this feature, we can fully support the 5th factor [2] of 12 factors cloud development which mandates the need to clearly separate build, release and run. The architecture we have in place *may be already able to support such feature as it already works in a step by step pipeline. The Integration move from a Build, Deploy and Run phase accordingly. The only thing is that we don't have a proper way to tell the operator to just Build and put in a kind of Ready (to run) Integration phase. I think we can enable this feature by letting the operator just stop once the container backing the Integration has been successfully built and pushed to the container registry (ie, with some Integration configuration, even an annotation). Then, the same operator (or any other using the same registry) could be able to run the Integration just executing the Deployment configuration (ie, those traits in charge to alter Kubernetes configuration). I don't see any immediate cons (unless there is a big development effort or important changes that we discover in a deeper analysis). The work on this feature may also cross with #5539, above all if we decide to move the source directly into the built container. [1] https://camel.zulipchat.com/#narrow/stream/257299-camel-k/topic/Using.20Camel.20K.20operator.20to.20build.20an.20image [2] https://12factor.net/build-release-run * to be verified with a deep analysis. ### Problem x ### Proposal _No response_ ### Open questions _No response_ -- 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]
