You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As suggested by @nicolaferraro in #583 (comment) and following-up on the initial work done in #125, a new build strategy could be implemented that would off-load the build controller logic in a separate service.
It will keep the advantages of the pod strategy, while enabling quicker builds scheduling and easy image layers and Maven dependencies caching.
It could be considered as a build operator, with a deployment owned by the Camel K operator that would embed the existing build controller, configured to use the existing routine strategy. Sidecaring could be considered for non-Kaniko publish strategy, if complexity stays low.
The text was updated successfully, but these errors were encountered:
astefanutti
changed the title
Build controller / service
Build controller service / operator
May 23, 2019
As suggested by @nicolaferraro in #583 (comment) and following-up on the initial work done in #125, a new build strategy could be implemented that would off-load the build controller logic in a separate service.
It will keep the advantages of the pod strategy, while enabling quicker builds scheduling and easy image layers and Maven dependencies caching.
It could be considered as a build operator, with a deployment owned by the Camel K operator that would embed the existing build controller, configured to use the existing
routine
strategy. Sidecaring could be considered for non-Kaniko publish strategy, if complexity stays low.The text was updated successfully, but these errors were encountered: