InseeFrLab / InseeFrLab/onyxia-api
Security : move away from "cluster-admin" everywhere
- Dominant language
- Java
- Stars
- 34
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Currently, `Onyxia-api` do everything (both `kubectl` and `helm`) using a single service account that is supposed to be cluster-admin.
Here are some improvements we could make :
* [x] Every regular `kubectl` and `helm` calls should be made using user's permissions
* [ ] Onboarding (creating user's namespace, applying permissions ...) should be done using a separate service account and preferably done in another process / pod (externalize the onboarding process as a standalone API ?)
* [ ] Try to reduce or at least refine and explicit permissions needed for the onboarding feature. Currently, it defaults to creating a cluster-admin service account which is probably too much
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.