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

[SPI] Add ability to create all user's workspaces in one OpenShift project #6284

Closed
sleshchenko opened this issue Sep 15, 2017 · 0 comments
Closed
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. target/branch Indicates that a PR will be merged into a branch other than master.

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Sep 15, 2017

Now we use one OpenShift project for OpenShift objects of one workspace. But it doesn't suit for some cases.
It is needed to add an ability to create all user's workspaces in one OpenShift project.
So there should be implemented different project choosing strategies:

  1. One OpenShift project for one workspace.
  2. One OpenShift project for all Che workspaces.
    There should be an ability to configure this strategy by external configuration.

To implement this it is needed to label all workspace objects which are related to one workspace with its id. To ensure that services use only pods from the same workspace should be solved by adding the same entry to Service#spec#selector field.

@akorneta akorneta added kind/task Internal things, technical debt, and to-do tasks to be performed. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. target/branch Indicates that a PR will be merged into a branch other than master. team/platform labels Sep 15, 2017
@benoitf benoitf changed the title Add ability to create all user's workspaces in one OpenShift project [SPI] Add ability to create all user's workspaces in one OpenShift project Sep 15, 2017
@akorneta akorneta self-assigned this Sep 20, 2017
@akorneta akorneta added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Sep 20, 2017
@akorneta akorneta removed the status/in-progress This issue has been taken by an engineer and is under active development. label Sep 25, 2017
@akorneta akorneta added the status/in-progress This issue has been taken by an engineer and is under active development. label Oct 9, 2017
@akorneta akorneta removed the status/in-progress This issue has been taken by an engineer and is under active development. label Oct 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. target/branch Indicates that a PR will be merged into a branch other than master.
Projects
None yet
Development

No branches or pull requests

3 participants