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.

Sign up for GitHub

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

Jump to bottom

Create a new olm channel in order to deploy Eclipse Che next version using DWO dependency and installMode: AllNamespaces #20455

Closed
flacatus opened this issue Sep 10, 2021 · 4 comments
Closed

Create a new olm channel in order to deploy Eclipse Che next version using DWO dependency and installMode: AllNamespaces #20455

flacatus opened this issue Sep 10, 2021 · 4 comments
Assignees
@AndrienkoAleksandr @flacatus
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/P2 Has a minor but important impact to the usage or development of the system.
Milestone
7.38

Comments

@flacatus
Copy link
Contributor

Is your task related to a problem? Please describe

Actaully we have stable-all-namespaces olm channel which deploy eclipse che in AllNamespace mode and with DWO dependency. The problem is we don't have a way to deploy che next in All Namespace mode with DWO olm dependency

Describe the solution you'd like

Create a new channel next-all-namespaces to deploy che in AllNamespace mode. This channel as next will not be pushed to community operators.

Describe alternatives you've considered

No response

Additional context

No response
@flacatus flacatus added kind/task Internal things, technical debt, and to-do tasks to be performed. area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator team/deploy labels Sep 10, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 10, 2021
@tolusha tolusha added sprint/next severity/P2 Has a minor but important impact to the usage or development of the system. and removed team/deploy labels Sep 10, 2021
@l0rd
Copy link
Contributor

l0rd commented Sep 10, 2021 •
edited
Loading

Ok so someone could use that channel doing:

chectl update next && \
chectl server:deploy  \
           --platform=openshift \
           --installer=olm \
           --olm-channel=next-all-namespaces

Hence a couple of questions:

  • Manually adding the che catalog source will be a prerequisite to use that command?
  • Does it make sense to remove chectl option --workspace-engine? I am asking because --olm-channel choice will also decide the workspace engine. And anyway at some point the devworkspcae will be the only choice.

@Katka92 Katka92 removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 13, 2021
@tolusha tolusha mentioned this issue Sep 14, 2021
Closed
29 tasks
@flacatus
Copy link
Contributor Author

flacatus commented Sep 16, 2021 •
edited
Loading

@l0rd
Sorry for delay.

Manually adding the che catalog source will be a prerequisite to use that command?

No, the chectl will add automatically the catalog for you in the cluster

Does it make sense to remove chectl option --workspace-engine? I am asking because --olm-channel choice will also decide the workspace engine. And anyway at some point the devworkspcae will be the only choice

To be honest we can remove this flag and use the channel to install the new devworkspace engine

@l0rd
Copy link
Contributor

l0rd commented Sep 16, 2021

To be honest we can remove this flag and use the channel to install the new devworkspace engine

@flacatus ok but maybe we will still need --workspace-engine for Kubernetes clusters that do not have OLM? Not sure what's the best way to handle that.

@flacatus
Copy link
Contributor Author

Ok, Maybe is better to mantain the flag until the devworkspace engine will be by default also in pure kubernetes.

@flacatus flacatus mentioned this issue Sep 20, 2021
Merged
11 tasks
@tolusha tolusha mentioned this issue Sep 27, 2021
Closed
27 tasks
@tolusha tolusha added this to the 7.38 milestone Sep 28, 2021
@AndrienkoAleksandr AndrienkoAleksandr self-assigned this Oct 7, 2021
@ibuziuk ibuziuk mentioned this issue Oct 7, 2021
Closed
@mmorhun mmorhun removed their assignment Oct 7, 2021
@AndrienkoAleksandr AndrienkoAleksandr mentioned this issue Oct 8, 2021
Merged
8 tasks
@tolusha tolusha mentioned this issue Oct 18, 2021
Closed
25 tasks
@tolusha tolusha closed this as completed Oct 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AndrienkoAleksandr AndrienkoAleksandr

@flacatus flacatus

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/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
7.38
Development

No branches or pull requests
7 participants
@l0rd @tolusha @AndrienkoAleksandr @mmorhun @Katka92 @che-bot @flacatus