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

OperatorHub stable channel must use "all-namespace" install mode #20866

Closed
4 of 5 tasks
Tracked by #20830
tolusha opened this issue Dec 1, 2021 · 9 comments
Closed
4 of 5 tasks
Tracked by #20830

OperatorHub stable channel must use "all-namespace" install mode #20866

tolusha opened this issue Dec 1, 2021 · 9 comments
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. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@tolusha
Copy link
Contributor

tolusha commented Dec 1, 2021

Is your task related to a problem? Please describe

OperatorHub stable channel must use "all-namespace" install mode.

Describe the solution you'd like

  • Set allNamespaces install mode for a stable channel.
  • Drop tech-preview channels
  • Provide migration guide from single to all namespaces mode
  • Adopt chectl
  • Adopt CI

Describe alternatives you've considered

No response

Additional context

[1] #20668

@tolusha tolusha 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 sprint/current severity/P1 Has a major impact to usage or development of the system. labels Dec 1, 2021
@tolusha tolusha added this to the 7.41 milestone Dec 1, 2021
@l0rd
Copy link
Contributor

l0rd commented Dec 1, 2021

@tolusha I think this morning we discussed that it may not be possible to publish "all-namespace" mode AND avoid automatic updates. If that's confirmed we should just stop publishing new releases on OperatorHub.

@tolusha
Copy link
Contributor Author

tolusha commented Dec 2, 2021

I've just checked. OLM doesn't allow to update from single namespace to all namespace mode

OwnNamespace InstallModeType not supported, cannot configure to watch own namespace

@tolusha
Copy link
Contributor Author

tolusha commented Dec 2, 2021

@l0rd
So, we can publish new releases on OperatorHub for a stable channel with allNamespace install mode.
Should we remove tech-preview channel ?

@l0rd
Copy link
Contributor

l0rd commented Dec 3, 2021

@tolusha 👍 to remove tech-preview channel

@l0rd
Copy link
Contributor

l0rd commented Jan 11, 2022

@tolusha do you plan to complete that in 7.42 rigth? I am asking to know if we can include that in the 7.42 release notes

@Kasturi1820
Copy link

Release Note text
The stable channel of Che operator has the DevWorkspace enabled by default and use the operator "all-namespace" installation mode. The other channels are being deleted.

@tolusha
Copy link
Contributor Author

tolusha commented Jan 12, 2022

There is the only one channel right now:

screenshot-console-openshift-console apps ci-ln-5dknrct-72292 origin-ci-int-gce dev rhcloud com-2022 01 12-12_15_05

I mark this issue as resolved. Doc will be tracked separately.

@tolusha tolusha closed this as completed Jan 12, 2022
@max-cx
Copy link

max-cx commented Jan 14, 2022

sync'd with Red Hat JIRA https://issues.redhat.com/browse/CRW-2646

@max-cx max-cx removed the status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording label Jan 12, 2023
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. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants