-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Reconcile roles #3810
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
Reconcile roles #3810
Conversation
For use during a rolling update, we'd also need an additive-only mode. I'd envision the flow as
|
That requires a covers evaluation, so it won't actually share code with this command. To illustrate: v1 grants get on foo. v2 grants get on bar. The --add-only grants get on foo and bar. I'd like to push that to another issue. |
Follow up is ok, but I think we need both before the upgrade scenario is complete |
It's not a stop-ship problem for 3.0.1 because our changes were strictly additive. |
@smarterclayton This is for a p1 issue (default policy changed between levels). Who can review? |
Make the default a dry run, and add |
9fc044c
to
048ace1
Compare
done. |
LGTM [merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/3723/) (Image: devenv-fedora_2048) |
[Test]ing while waiting on the merge queue |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/3723/) |
Evaluated for origin up to a7b0509 |
Merged by openshift-bot
Fixes #3802.
This adds
oadm policy reconcile-cluster-roles
. This command ensures that every recommended bootstrap cluster role exists with the correct ruleset. You can pass an-o yaml|json
to output what would be changed instead of actually making the changes. That list can then be passed tooc replace --force
to make the changes.