Remove requirement for cluster-admin for tiller in openshift example. #1265
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #676 .
This PR fixes one remaining issue I had with the development environment on OpenShift, removing the need to use
cluster-admin
for tiller. Together with the work from the past iteration, Kubeapps now installs without issue on OpenShift.I'm not keen to make a stronger statement about OpenShift support for a few reasons, so have updated the relevant part of the troubleshooting in the README to mention our tentative support and link to the RBAC policies as examples for the related issue.
As per TODOs in the doc, I don't think the RBAC requirements are specific to OpenShift, but rather we should be promoting these as the default (for helm2 / tiller - we don't seem to mention working with non-cluster-admin tiller anywhere that I can see. Checked our access-control doc but that is Kubeapps specific)