Skip to content

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

Merged
merged 1 commit into from
Jul 23, 2015
Merged

Reconcile roles #3810

merged 1 commit into from
Jul 23, 2015

Conversation

deads2k
Copy link
Contributor

@deads2k deads2k commented Jul 21, 2015

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 to oc replace --force to make the changes.

@liggitt
Copy link
Contributor

liggitt commented Jul 21, 2015

For use during a rolling update, we'd also need an additive-only mode. I'd envision the flow as

reconcile-cluster-roles --add-only
# do the master upgrades
reconcile-cluster-roles

@deads2k
Copy link
Contributor Author

deads2k commented Jul 21, 2015

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.

@liggitt
Copy link
Contributor

liggitt commented Jul 21, 2015

Follow up is ok, but I think we need both before the upgrade scenario is complete

@deads2k
Copy link
Contributor Author

deads2k commented Jul 21, 2015

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.

@deads2k
Copy link
Contributor Author

deads2k commented Jul 22, 2015

@smarterclayton This is for a p1 issue (default policy changed between levels). Who can review?

@smarterclayton
Copy link
Contributor

Make the default a dry run, and add --confirm

@deads2k deads2k force-pushed the reconcile-roles branch 2 times, most recently from 9fc044c to 048ace1 Compare July 22, 2015 19:20
@deads2k
Copy link
Contributor Author

deads2k commented Jul 22, 2015

Make the default a dry run, and add --confirm

done.

@smarterclayton
Copy link
Contributor

LGTM [merge]

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/3723/) (Image: devenv-fedora_2048)

@openshift-bot
Copy link
Contributor

[Test]ing while waiting on the merge queue

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/3723/)

@openshift-bot
Copy link
Contributor

Evaluated for origin up to a7b0509

openshift-bot pushed a commit that referenced this pull request Jul 23, 2015
@openshift-bot openshift-bot merged commit 56012d9 into openshift:master Jul 23, 2015
@deads2k deads2k deleted the reconcile-roles branch July 31, 2015 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants