-
Notifications
You must be signed in to change notification settings - Fork 21
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
fix: used dedicated clusterrole for kcore hooks #1635
Conversation
This repo has @d2iq-mergebot integration. You can perform the following commands by submitting a comment. Submit a comment with content "@d2iq-mergebot help" to view more detailed help text and examples. Be sure the have a look at the mergebot documentation, too.For help using mergebot, please refer to the README file here: https://github.com/mesosphere/mergebot/blob/main/README.md |
91a2dfa
to
ba63db9
Compare
52a5b8c
to
e9e95e1
Compare
Pull Request Test Coverage Report for Build 6314939967
💛 - Coveralls |
* Revert "fix: used dedicated clusterrole for kcore hooks (#1635)" This reverts commit 6d2c1f3. * Revert "feat: patch kcore status to kommander ver pre upgrade (#1608)" This reverts commit 585e249. * fix: use dedicated clusterrole for kcore hooks * chore: add patch & update for post install job --------- Co-authored-by: York Chen <[email protected]>
depends on #1608
What problem does this PR solve?:
the kommandercore related jobs have been using cluster-admin clusterrole. although it's short lived, it's better to just drop that usage.
Which issue(s) does this PR fix?:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Checklist