Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update updater roles necessary for non-operator based viziers (#1578)
Summary: The role refactors in ff26221 and then later 87b7751 caused us to drop some ClusterRoles that the updater relied on to upgrade viziers that don't have an operator. I believe the initial breakage was caused by ff26221 since it no longer included the necessary clusterrole, however it referenced an old clusterrole which meant that upgrades worked on clusters that had the old role. 87b7751 then removed the binding to the old seemingly non-existent clusterrole while then broke upgrades further. This attempts to add back the necessary permissions to unbreak such deploys. Note that even with this change, I believe anyone running a non-operator deploy of vizier that was first deployed after v0.12.6 won't be able to auto-upgrade to any newer versions unless they manually patch the roles and clusterroles for the updater service account. Type of change: /kind bug Test Plan: Deployed a vizier on a freshly created cluster. Removed any traces of the CRD, olm, operator. Updated the roles and clusterroles by patching in this change on the cluster. Used the `px` CLI to upgrade said vizier to an RC, ensured that the non-operator Job based upgrade triggered and succeeded. Changelog Message: ```release-note This release adds additional ClusterRoles and Roles that the `vizier-upgrade-job` needs to upgrade Viziers deployed without an operator. ``` Signed-off-by: Vihang Mehta <[email protected]>
- Loading branch information