squakez opened a new issue, #5967: URL: https://github.com/apache/camel-k/issues/5967
### Requirement The necessity to support the `routine` building strategy is a kind of a limitation as it requires the operator to be able to manage the operations concerns and the build concern, delegating this to some external Maven processes but on the same running Pod. I think that we should remove the support of `routine` entirely, letting the operator to spin off a Pod and perform the build accordingly as it already happens with `pod` strategy. This would simplify the design and maintenance of the project and likely the usage of the operator with one less concern to care. Anyway it would be something to consider in a major release only. Feedback are welcome. ### Problem a ### 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: commits-unsubscr...@camel.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
