-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Osa cluster admin #9058
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
Osa cluster admin #9058
Conversation
* adding cluster admin option to osa create * adding direcctory read permissions to the aad app * making active directory app always require directory permissions * infra node to 3
* adding cluster admin option to osa create * adding direcctory read permissions to the aad app * making app always require directory permissions * clean + infra node to 3 * fixing typo * using new version of acs python sdk
mboersma
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good Jack, I had a couple minor comments.
| short-summary: The CIDR used on the Subnet into which to deploy the cluster. | ||
| - name: --customer-admin-group-id | ||
| type: string | ||
| short-summary: The ID of an Azure Active Directory Group that memberships will get synced into the OpenShift group "osa-customer-admins". If not specified no cluster admin access will be granted |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you change the second sentence here to have a comma and end with a period?
If not specified, no cluster admin access will be granted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like this was already updated
| agent_infra_pool_profile = OpenShiftManagedClusterAgentPoolProfile( | ||
| name='infra', # Must be 12 chars or less before ACS RP adds to it | ||
| count=int(2), | ||
| count=int(3), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this change the default node pool count from 2 to 3? That seems like a significant change (not related to this PR). Maybe it should be mentioned separately in the release notes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we agreed on this to switch from 2 to 3
yugangw-msft
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor comments. Please address and I will merge
|
|
||
| 2.3.20 | ||
| ++++++ | ||
| * adding customer-admin-group-id flag to az osa create |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please move to the top
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, moved to top as 2.3.22 and bumped version
| short-summary: The CIDR used on the Subnet into which to deploy the cluster. | ||
| - name: --customer-admin-group-id | ||
| type: string | ||
| short-summary: The ID of an Azure Active Directory Group that memberships will get synced into the OpenShift group "osa-customer-admins". If not specified, no cluster admin access will be granted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i believe it should be the object id of the AAD group? If yes, please make it clear
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated description
| - name: Create an OpenShift cluster and auto create an AAD Client | ||
| text: az openshift create -g MyResourceGroup -n MyManagedCluster --fqdn {FQDN} | ||
| - name: Create an OpenShift cluster and auto create an AAD Client and setup cluster admin group | ||
| text: az openshift create -g MyResourceGroup -n MyManagedCluster --fqdn {FQDN} --customer-admin-group-id {GROUP_ID} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is going to be incompatible with PR #9083 which removes FQDN.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tjprescott FQDN is not being removed. Its being made optional. PR #9083 will be done on top of this PR.
| additional_properties=None, type="Scope") | ||
| required_osa_aad_access = RequiredResourceAccess(resource_access=[resource_access], | ||
| # Read directory permissions on Windows Azure Active Directory API | ||
| directory_access = ResourceAccess(id="5778995a-e1bf-45b8-affa-663a9f3f4d04", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this hard-coded ID?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this hard-coded ID?
@tjprescott these are scope GUIDs for programmatic use and represent various permissions: https://docs.microsoft.com/en-us/graph/permissions-reference. Currently there isn't a straightforward documentation from AAD for this and this is obtained by looking at currently configured apps in AAD.
# Conflicts: # src/command_modules/azure-cli-acs/HISTORY.rst # src/command_modules/azure-cli-acs/setup.py
|
@yugangw-msft @mboersma comments addressed by @sozercan. PTAL |
|
From the CI failures, maybe we just need to re-record the Edit: or all of them. |
This reverts commit 8643736.
# Conflicts: # src/command_modules/azure-cli-acs/setup.py
|
@tjprescott any ideas why |
|
@tjprescott @yugangw-msft tests are green now |
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).
I adhere to the Command Guidelines.