ChrWeissDe opened a new issue, #3551: URL: https://github.com/apache/camel-k/issues/3551
We have the requirements in multiple projects to stage Camel-K Integraton along with their created docker image across multiple Kubernetes clusters. Reason is that the cutsomers have got dedicated cluster for dev, test, pre-prod and prod. Further they want to avoid the rebuild of the Integrations (incl. the creation of a new docker image) on the different stages. Reason are here regulatory or own operational requirements. To achieve this it would be good to have a clear "Camel-K supported/provided process" with "tooling support". Additional assumptions / prereqs: - image registry is already shared across the clusters See also the initial discussion in the Camel-K User Group: https://lists.apache.org/thread/wkvzwxgnqfyqz0zbrljg3dppl4ppsdc4 -- 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
