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

Develop technical plan for DevWorkspaceCRD introducing #15522

Closed
sleshchenko opened this issue Dec 18, 2019 · 1 comment
Closed

Develop technical plan for DevWorkspaceCRD introducing #15522

sleshchenko opened this issue Dec 18, 2019 · 1 comment
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

Is your task related to a problem? Please describe.

DevWorkspaceCRD already has some initial implementation/draft proposal https://github.com/che-incubator/devworkspace-api
It's needed to learn more about it and develop some technical plan how to can move K8s/OS infrastructure to DevWorkspace Controller.

More see epic #15425

@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. labels Dec 18, 2019
@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 Dec 18, 2019
@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 Dec 18, 2019
@sleshchenko sleshchenko self-assigned this Dec 18, 2019
@sleshchenko sleshchenko moved this from TODO to In progress in Controller team sprint #177 Dec 21, 2019
@sleshchenko
Copy link
Member Author

During this task several improvements were made:

Also, working on this issue gave a bigger picture of what we have now but I believe it's not time where we can define full and detailed enough technical plan for DevWorkspaceCRD.
So, the current priority is to adapt DevWorkspace Controller to CloudShell needs, some of needed issues are already created under the following epic: #15434
And we'll extend this list later.
So, we're focusing on CloudShell needs but keep in mind the future of DevWorkspace in general, but plan how we can replace K8s infrastructure with DevWorkspace Controller will be made later.

@sleshchenko sleshchenko moved this from In Progress to Completed in Controller team sprint #178 Jan 23, 2020
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
No open projects
Development

No branches or pull requests

3 participants