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

Allow OLM installation through CatalogSource and related docker image #15802

Closed
davidfestal opened this issue Jan 23, 2020 · 3 comments
Closed

Allow OLM installation through CatalogSource and related docker image #15802

davidfestal opened this issue Jan 23, 2020 · 3 comments
Assignees
@flacatus
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator 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.

Comments

@davidfestal
Copy link
Contributor

Is your enhancement related to a problem? Please describe.

Currently we can only install Che on OLM with an OperatorSource that points to a related Quay.io application.
This makes automated testing of OLM installations / updates uneasy.

Describe the solution you'd like

We should also build the required docker image of a dedicated catalog, in order to install directly through a CatalagSource, as described in https://github.com/operator-framework/operator-registry

Describe alternatives you've considered

Additional context
@davidfestal davidfestal added kind/enhancement A feature request - must adhere to the feature request template. area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator team/deploy labels Jan 23, 2020
@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 Jan 23, 2020
@davidfestal davidfestal mentioned this issue Jan 23, 2020
Closed
@tolusha tolusha added this to the Backlog - Deploy milestone Jan 23, 2020
@tolusha tolusha added severity/P1 Has a major impact to usage or development of the system. sprint/next sprint/current and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. sprint/next labels Jan 23, 2020
@tolusha tolusha mentioned this issue Jan 27, 2020
Closed
35 tasks
@flacatus
Copy link
Contributor

flacatus commented Feb 4, 2020

Inside of OLM folder we have some files whit this extension: *.yaml.diff and when we build the dockerfile with operator-framework failed because the operator is trying to read this files like a yaml files. Should keep this files or delete them?
PD: EG (https://github.com/eclipse/che-operator/blob/master/olm/eclipse-che-preview-kubernetes/deploy/olm-catalog/eclipse-che-preview-kubernetes/7.8.0/eclipse-che-preview-kubernetes.v7.8.0.clusterserviceversion.yaml.diff)

@tolusha
Copy link
Contributor

tolusha commented Feb 4, 2020

we should keep them

@tolusha
Copy link
Contributor

tolusha commented Feb 7, 2020

@flacatus
Pls link all PRs related to this issue

@tolusha tolusha removed this from the Backlog - Deploy milestone Feb 11, 2020
@tolusha tolusha closed this as completed Feb 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flacatus flacatus

Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator 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
Milestone
No milestone
Development

No branches or pull requests
4 participants
@davidfestal @tolusha @che-bot @flacatus