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

Provide SOP for migration of existing eclipse che instancies from the 'stable' to 'next' (all-namespaces) channel #20602

Closed
Tracked by #20648
ibuziuk opened this issue Oct 7, 2021 · 1 comment
Assignees
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Oct 7, 2021

Is your task related to a problem? Please describe

a new olm channel in order to deploy Eclipse Che next version using DWO dependency and installMode: AllNamespaces has been created as part of #20455
However, currently, it is not clear how exactly migrate existing che instances installed from Operatorhub via a stable channel to the the next one

Describe the solution you'd like

Provide SOP for migration of the existing eclipse-che instancies installed from the OperatorHub to the new next channel

Describe alternatives you've considered

N/A

Additional context

a new olm channel in order to deploy Eclipse Che next version using DWO dependency and installMode: AllNamespaces has been created as part of #20455

@ibuziuk ibuziuk added kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator labels Oct 7, 2021
@tolusha tolusha mentioned this issue Oct 18, 2021
25 tasks
@AndrienkoAleksandr AndrienkoAleksandr self-assigned this Nov 19, 2021
@ibuziuk ibuziuk changed the title Provide SOP for migration of existing eclipse che instancies from the 'stable' to 'next' channel Provide SOP for migration of existing eclipse che instancies from the 'stable' to 'next' (all-namespaces) channel Nov 25, 2021
@tolusha tolusha mentioned this issue Nov 29, 2021
28 tasks
@tolusha tolusha mentioned this issue Dec 28, 2021
14 tasks
@tolusha tolusha mentioned this issue Jan 10, 2022
28 tasks
@tolusha tolusha mentioned this issue Jan 31, 2022
18 tasks
@ibuziuk ibuziuk mentioned this issue Mar 15, 2022
35 tasks
@ibuziuk ibuziuk mentioned this issue Apr 6, 2022
45 tasks
@ibuziuk
Copy link
Member Author

ibuziuk commented Apr 12, 2022

Fixed as part of eclipse-che/che-docs#2269

@ibuziuk ibuziuk closed this as completed Apr 12, 2022
@ibuziuk ibuziuk mentioned this issue Apr 25, 2022
58 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants