You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "squakez (via GitHub)" <gi...@apache.org> on 2024/11/28 17:36:22 UTC
[I] Drop support for `routine` versus `pod` building strategy [camel-k]
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-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Drop support for `routine` versus `pod` building strategy [camel-k]
Posted by "timmy-mathew-ah (via GitHub)" <gi...@apache.org>.
timmy-mathew-ah commented on issue #5967:
URL: https://github.com/apache/camel-k/issues/5967#issuecomment-4158517609
Fully agree and support the decision of standardizing on the `POD` strategy as the default going forward and remove `ROUTINE` strategy. It cleanly separates concerns by delegating builds to dedicated Pods. This also improves scalability and resource control especially under concurrent workloads.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org