Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Canary rollout upgrade #2371

Open
5 of 7 tasks
astefanutti opened this issue Jun 7, 2021 · 2 comments
Open
5 of 7 tasks

Canary rollout upgrade #2371

astefanutti opened this issue Jun 7, 2021 · 2 comments
Assignees
Labels
area/core Core features of the integration platform area/installation Installation and Topology area/managed-service Camel K as a Managed Service status/never-stale

Comments

@astefanutti
Copy link
Member

astefanutti commented Jun 7, 2021

This is a shell issue, that gathers the technical gaps, identified to implement Camel K operator canary rollout upgrade:

The implementation should work equally for both OLM and standalone (kamel install or kustomize) installation modes.

@astefanutti astefanutti added the area/installation Installation and Topology label Jun 7, 2021
@astefanutti astefanutti self-assigned this Jun 8, 2021
@astefanutti astefanutti added area/core Core features of the integration platform area/managed-service Camel K as a Managed Service labels Sep 22, 2021
@github-actions
Copy link
Contributor

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!

@lburgazzoli
Copy link
Contributor

Relates to #3397 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core Core features of the integration platform area/installation Installation and Topology area/managed-service Camel K as a Managed Service status/never-stale
Projects
None yet
Development

No branches or pull requests

3 participants