-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Track bootstrap policy updates / migration #3717
Comments
@deads2k fyi |
@adellape We're adding a command to update the bootstrap roles as a post-update step. Final shape is tbd, but #3810 is where it lives. Do you know where we'd normally document this sort of command? @sdodson @detiber This command has a dry-run functionality that produces empty output when no changes are needed and json or yaml output with new roles when it is needed. Can you make use of this sort of a command to help users know they might want to look at updating their policy? |
@deads2k At first glance, I would think an initial mention / explanation of the situation & command near the end of https://docs.openshift.org/latest/architecture/additional_concepts/authorization.html#roles. And if the use case is mostly within the context of cluster upgrades, then tasks / example usage probably should be part of the WIP upgrade docs @sdodson has started here: openshift/openshift-docs#731 (and cross-link between the Arch topic). |
Opened openshift/openshift-docs#792 Added a comment to openshift/openshift-docs#731. Once #3810 merges, I think we're good. |
@deads2k Copied things into the upgrade doc, i'll gather some example output once your change merges and it's easy for me to gather. |
fixed. |
Need to document and determine how to update bootstrap roles with new permissions per release.
Updates since 1.0.0:
/oapi
post
onpods/portforward
,pods/exec
The text was updated successfully, but these errors were encountered: