You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/08/18 08:36:44 UTC
[GitHub] [camel-k] ChrWeissDe opened a new issue, #3551: Staging of Camel-K Integration across multiple cluster
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-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3551: Staging of Camel-K Integration across multiple cluster
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #3551:
URL: https://github.com/apache/camel-k/issues/3551#issuecomment-1705044129
The scenario is illustrated in https://camel.apache.org/blog/2023/07/camel-k-gitops/ - if that is not yet a possible solution, feel free to reopen.
--
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
[GitHub] [camel-k] github-actions[bot] commented on issue #3551: Staging of Camel-K Integration across multiple cluster
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #3551:
URL: https://github.com/apache/camel-k/issues/3551#issuecomment-1317864219
This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!
--
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
[GitHub] [camel-k] squakez closed issue #3551: Staging of Camel-K Integration across multiple cluster
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #3551: Staging of Camel-K Integration across multiple cluster
URL: https://github.com/apache/camel-k/issues/3551
--
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