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

Che operator should support single-user Che #13420

Closed
l0rd opened this issue May 26, 2019 · 6 comments
Closed

Che operator should support single-user Che #13420

l0rd opened this issue May 26, 2019 · 6 comments
Assignees
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.
Milestone

Comments

@l0rd
Copy link
Contributor

l0rd commented May 26, 2019

Description

Currently Che operator supports only multi-user Che. To avoid maintaining both the operator and the legacy DeploymentConfig we should update the operator to support single-user Che and deprecate the DeploymentConfig.

@davidfestal can you have a look at this issue when you have merged operator-framework/community-operators#384 and operator-framework/community-operators#383

cc @nickboldt @ibuziuk

@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. team/osio labels May 26, 2019
@ibuziuk
Copy link
Member

ibuziuk commented May 27, 2019

@l0rd hmm, interesting - I thought we were going to deprecate single-user [1] in general, so not really following why having single-user based operator-driven deployment is a GA priority

[1] #10996

@l0rd
Copy link
Contributor Author

l0rd commented May 27, 2019

I am ok to close this issue if we can deprecate single user before GA. But I am not aware of a solution for deprecating single user yet. What I know is that we can deprecate che_deploy.sh if we can use the operator for single-user. That should be easy to implement and would mean one less installer to maintain...Does that make sense?

@ibuziuk
Copy link
Member

ibuziuk commented May 27, 2019

this makes sense. Am I correct that operator based deployment would support both OpenShift 4 and OpenShift 3.11 ?

@davidfestal
Copy link
Contributor

yes afaik

@nickboldt
Copy link
Contributor

nickboldt commented May 29, 2019 via email

@l0rd
Copy link
Contributor Author

l0rd commented May 29, 2019

OLM is included as a component of OS 4.x
OLM is not included but can be installed on OpenShift 3.11 (c.f. the doc)

@l0rd l0rd added this to the 7.x milestone Jul 2, 2019
@skabashnyuk skabashnyuk modified the milestones: 7.x, 7.3.0 Aug 29, 2019
@l0rd l0rd modified the milestones: 7.3.0, 7.2.0 Aug 29, 2019
@l0rd l0rd added the severity/P1 Has a major impact to usage or development of the system. label Aug 29, 2019
@skabashnyuk skabashnyuk modified the milestones: 7.2.0, 7.3.0 Sep 5, 2019
@skabashnyuk skabashnyuk added area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator and removed team/platform labels Sep 23, 2019
@benoitf benoitf modified the milestones: 7.3.0, Backlog - Hosted Che Oct 30, 2019
@sleshchenko sleshchenko modified the milestones: Backlog - Hosted Che, Backlog - Deploy Jan 22, 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 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

8 participants