Support one namespace per user strategy (che.osio like)
See original GitHub issueCurrently a Che admin has 2 options to specify in what namespace the workspaces pods will be started:
- Use one namespace for all the workspace of every Che user (security issue)
- Create a new namespace for every new workspaces (resources issue)
An approach that looks like more suitable for most real-world use cases is to deploy all workspaces pods of a given user in one of the user namespaces. That’s the approach that has been implemented for che.openshift.io.
That has the merit to make it closer to have an upstream che
/ che osio
parity (c.f. #13265)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:17 (15 by maintainers)
Top Results From Across the Web
Kubernetes Namespace: How To Use It To Organize And ...
Learn how to use a Kubernetes namespace strategy to organize your clusters better and control your cloud costs.
Read more >User Namespaces - Kubernetes
This page explains how user namespaces are used in Kubernetes pods. A user namespace allows to isolate the user running inside the container ......
Read more >Best Practices for Kubernetes Namespaces - Appvia
Best Practices for Kubernetes Namespaces · About the List · Use Semantic, Scalable Names · Don't Put Everything in the Default Namespace ·...
Read more >Kubernetes Namespaces Demystified - How To Make The ...
Namespaces allow the kernel to assign group attributes to a single or multiple processes. The feature works by having a single namespace for ......
Read more >Kubernetes best practices: Specifying Namespaces in YAML
You can think of a Namespace as a virtual cluster inside your Kubernetes cluster. You can have multiple namespaces inside a single ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kameshsampath will create a separate issue about that. @slemeur any comments about that https://github.com/eclipse/che/issues/13488#issuecomment-527200019 ?
@rkratky The above location looks right to me but is there anything I am missing?