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

chectl "next" channel with OLM installer should install nightly Che. #17183

Closed
AndrienkoAleksandr opened this issue Jun 18, 2020 · 1 comment
Closed
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator area/chectl Issues related to chectl, the CLI of Che kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@AndrienkoAleksandr
Copy link
Contributor

AndrienkoAleksandr commented Jun 18, 2020

Is your enhancement related to a problem? Please describe.

During some transition period, we implemented installation"latest" Che for chectl "next" channel, with warning about that. Ideally we should do installation "nightly" Che for "next channel". It should be useful for testing Che via olm installer.

Describe the solution you'd like

We can set up for https://github.com/eclipse/che-operator nightly job to push Eclipse Che preview CatalogSource image and use this image in the chectl to install "nightly" Che. Prototype of such images was implemented by QA https://github.com/eclipse/che-operator/blob/master/olm/eclipse-che-preview-kubernetes/Dockerfile and https://github.com/eclipse/che-operator/blob/master/olm/eclipse-che-preview-openshift/Dockerfile

Describe alternatives you've considered

We can use quay.io application registry and OperatorSource to install nightly Che, but OperatorSource is depracated and seems it was even removed from the latest OLM manager. So it is an option, but I would say - very bad option.

@AndrienkoAleksandr AndrienkoAleksandr added the kind/enhancement A feature request - must adhere to the feature request template. label Jun 18, 2020
@AndrienkoAleksandr
Copy link
Contributor Author

I think implementation should have to steps:

  • set up nightly ci to push images
  • use CatalogSource images in the chectl

@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 Jun 18, 2020
@mmorhun mmorhun added this to the Backlog - Deploy milestone Jun 18, 2020
@rhopp rhopp added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jun 19, 2020
@tolusha tolusha modified the milestone: Backlog - Deploy Jul 9, 2020
@l0rd l0rd added area/chectl Issues related to chectl, the CLI of Che area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator labels Jul 29, 2020
@tolusha tolusha modified the milestones: Backlog - Deploy, 7.18 Aug 11, 2020
@tolusha tolusha mentioned this issue Aug 11, 2020
42 tasks
@tolusha tolusha mentioned this issue Aug 19, 2020
58 tasks
@tolusha tolusha modified the milestones: 7.18, 7.19 Aug 26, 2020
@tolusha tolusha mentioned this issue Sep 8, 2020
48 tasks
@tolusha tolusha modified the milestones: 7.19, 7.20 Sep 11, 2020
@tolusha tolusha modified the milestones: 7.20, 7.19 Sep 14, 2020
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 area/chectl Issues related to chectl, the CLI of Che kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

6 participants