-
Notifications
You must be signed in to change notification settings - Fork 179
Rename ClusterRole and ClusterRoleBinding #3002
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename ClusterRole and ClusterRoleBinding #3002
Conversation
✅ Deploy Preview for docs-securecodebox ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
This pull request includes breaking changes. Please make sure that you included the breaking changes and the steps required to upgrade in Upgrading. |
3abe5ed to
1de62fe
Compare
Rename the ClusterRole 'manager-role' and ClusterRoleBinding 'manager-rolebinding' to 'securecodebox-manager-role' and 'securecodebox-manager-rolebinding', respectively, because the original names are too generic and could collide with other projects in the same cluster. Signed-off-by: Boris Shek <boris.shek@iteratec.com>
1de62fe to
632942e
Compare
…g in upgrading.md Add a "From 4.X to 5.X" section in upgrading.md. Add an explanation that the operator’s ClusterRole 'manager-role' and ClusterRoleBinding 'manager-rolebinding' have been renamed to 'securecodebox-manager-role' and 'securecodebox-manager-rolebinding'. Signed-off-by: Boris Shek <boris.shek@iteratec.com>
|
|
Resolves #2621 |
|
looks go
8000
od :) |



Rename the ClusterRole 'manager-role' and ClusterRoleBinding 'manager-rolebinding' to 'securecodebox-manager-role' and 'securecodebox-manager-rolebinding', respectively, because the original names are too generic and could collide with other projects in the same cluster.
Description
Checklist