Clarify documentation regarding RBAC
The documentation does not provide clarity for determining when RBAC is in play, and how to verify. This causes two problems:
- If RBAC is present, and you don't use the preparation steps,
helm install
will fail with a useless message (No avalable release found
) and you have to go check the Tiller pod logs for the real cause. - If RBAC is not present, you won't be able to install the RBAC related items
We need to document:
- how to determine RBAC present and active
- a methodology for applying RBAC, post failure. (
helm init --upgrade --service-account xx
) - Clearly delineate between commands to use depending on status of RBAC (such as
helm init
) - Use the cp command to work with the rbac role, rather than a link to where it lives on gitlab.com
We should also restructure the documentation to assume that RBAC is usually enabled.
- Restructure so that if you would end up in the setting up rbac setting if you were unsure
Edited by DJ Mountney