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

Document how to use one namespace per user strategy (che.osio like) #14624

Closed
skabashnyuk opened this issue Sep 23, 2019 · 2 comments
Closed
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@skabashnyuk
Copy link
Contributor

skabashnyuk commented Sep 23, 2019

Is your task related to a problem? Please describe.

In this pr #14524 we introduced some features that give more control over #13488 one namespace per user strategy (che.osio like). As discussed here #13488 (comment) we need

  • We need to update documentation explaining how to do that and what is the benefits from that.
  • add a note to the documentation that compatible PVC strategies are: unique, common and perWorkspace

Describe the solution you'd like

PR in che-docs

Describe alternatives you've considered

n/a

Additional context

n/a

@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform severity/P1 Has a major impact to usage or development of the system. labels Sep 23, 2019
@skabashnyuk skabashnyuk added this to the 7.2.0 milestone Sep 23, 2019
@sparkoo
Copy link
Member

sparkoo commented Sep 23, 2019

here's global che docs overview task https://github.com/eclipse/che-docs/issues/712. "Configuring namespace strategies" is blocker for this.

@sparkoo
Copy link
Member

sparkoo commented Oct 1, 2019

fixed by eclipse-che/che-docs#825

@sparkoo sparkoo closed this as completed Oct 1, 2019
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. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

2 participants