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

[dev-workspace] Set up OLM installation for OpenShift Terminal Operator #16311

Closed
sleshchenko opened this issue Mar 11, 2020 · 2 comments
Closed
Assignees
Labels
engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/task Internal things, technical debt, and to-do tasks to be performed.

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Mar 11, 2020

Is your task related to a problem? Please describe.

Currently we have deploy/olm-catalog configuration files but they are out-dated.
So, deploy/olm-catalog needs to be regenerated via operator-sdk, but refactorings have made this tricky, as it depends on a single operator.yaml (and we have two -- deploy/os/controller.yaml and deploy/k8s/controller.yaml.

@sleshchenko sleshchenko added kind/task Internal things, technical debt, and to-do tasks to be performed. engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. team/controller labels Mar 11, 2020
@l0rd l0rd mentioned this issue Mar 11, 2020
38 tasks
@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 Mar 11, 2020
@sleshchenko sleshchenko removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 11, 2020
@sleshchenko sleshchenko changed the title [dev-workspace] Set up OLM installation for WorkspaceOperator [dev-workspace] Set up OLM installation for OpenShift Terminal Operator May 28, 2020
@sleshchenko
Copy link
Member Author

  1. Create a git repo under redhat-developers.
  2. Figure out if we should just more the made PR Make operator installable via olm devfile/devworkspace-operator#83 or merge is and duplicate the same for OpenShift Terminal Operators.
  3. Investigate migration of controller from OpenShift Operator to Workspace Operator when OpenShift Operator just depends on Workspace.

@sleshchenko
Copy link
Member Author

It's mainly implemented withing redhat-developer/web-terminal-operator#1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

No branches or pull requests

3 participants