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

By default create users namespaces using Che ServiceAccount #19717

Closed
skabashnyuk opened this issue Apr 29, 2021 · 0 comments · Fixed by eclipse-che/che-server#7
Closed

By default create users namespaces using Che ServiceAccount #19717

skabashnyuk opened this issue Apr 29, 2021 · 0 comments · Fixed by eclipse-che/che-server#7
Assignees
Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes status/release-notes-review-done Issues that have been reviewed by the doc team for the Release Notes wording
Milestone

Comments

@skabashnyuk
Copy link
Contributor

skabashnyuk commented Apr 29, 2021

Is your task related to a problem? Please describe.

At this moment when OpenShift OAuth is enabled che-server creating a namespace on behalf of the user's SA.
That brings a lot of manual work for the cluster admins in case if namespaces provisioning is not allowed for the users.
Desired user's permissions in a newly created namespace - TBD

Describe the solution you'd like

Consider creating user namespaces with che-server's SA even when OpenShift OAuth is enabled

Describe alternatives you've considered

n/a

Additional context

Release Notes Text

By default Che now creates users namespaces using Che ServiceAccount, even if OpenShift OAuth is enabled. This will avoid failures when users don't have enough privileges to create namespaces. An administrator can still change the default and configure Che to create namespaces using users tokens.

@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. area/che-server team/platform sprint/next labels Apr 29, 2021
@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 Apr 29, 2021
@skabashnyuk skabashnyuk removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Apr 30, 2021
@skabashnyuk skabashnyuk added this to the 7.31 milestone May 5, 2021
@skabashnyuk skabashnyuk self-assigned this May 6, 2021
@skabashnyuk skabashnyuk modified the milestones: 7.31, 7.32 May 26, 2021
@l0rd l0rd added new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording labels Jun 15, 2021
@l0rd l0rd changed the title Consider creating user namespaces with che-server's SA even when OpenShift OAuth is enabled Always create users namespaces using Che ServiceAccount Jun 15, 2021
@l0rd l0rd changed the title Always create users namespaces using Che ServiceAccount By default create users namespaces using Che ServiceAccount Jun 15, 2021
@themr0c themr0c added status/release-notes-review-done Issues that have been reviewed by the doc team for the Release Notes wording and removed status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording labels Jun 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes status/release-notes-review-done Issues that have been reviewed by the doc team for the Release Notes wording
Projects
None yet
4 participants