Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[DevWorkspace] Make it possible to bind namespace role to a namespace service-account
See original GitHub issueIs your task related to a problem? Please describe
When provisioning a namespace, Che sets serviceAccountName as che-workspace, but in the DevWorkspace installation we have another Service Account like workspace<workspace id>-sa which is actually used for a workspace. So when creating a role binding it is binded to the che-workspace service account, but when I make a kubernetes request from a workspace container it is using a token of the workspace<workspace id>-sa service account.
Describe the solution you’d like
Need to have a way to bind namespace roles to a namespace service-account.
Describe alternatives you’ve considered
No response
Additional context
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
There is no technical reason for storing preferences in secret but not in config-map, so I am +1 to have a config-map
workspace-preferences-configmap.Closing as https://github.com/devfile/devworkspace-operator/pull/675 is merged