It would be good to support authorization of separate users in yipee. The current implementation assumes that any yipee user is essentially "super-user". The default yipee.yaml grants broad permissions to the yipee-service-account allowing read/write/delete access to most cluster objects.
A better approach would be to define per-user access permissions via Kubernetes RBAC and teach yipee to act as a given user when performing cluster operations
It would be good to support authorization of separate users in yipee. The current implementation assumes that any yipee user is essentially "super-user". The default yipee.yaml grants broad permissions to the yipee-service-account allowing read/write/delete access to most cluster objects.
A better approach would be to define per-user access permissions via Kubernetes RBAC and teach yipee to act as a given user when performing cluster operations