-
Notifications
You must be signed in to change notification settings - Fork 359
updating the RBAC +ABAC scenario of ACR #510
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
@@ -115,6 +115,18 @@ An online deployment runs your user container with the endpoint identity, that i | |||||||||||||||||||||
- For a SAI, the identity is created automatically when you create the endpoint, and roles with fundamental permissions, such as the Container Registry pull permission **AcrPull** and the **Storage Blob Data Reader**, are automatically assigned. | ||||||||||||||||||||||
- For a UAI, you need to create the identity first, and then associate it with the endpoint when you create the endpoint. You're also responsible for assigning proper roles to the UAI as needed. | ||||||||||||||||||||||
|
||||||||||||||||||||||
> [!IMPORTANT] | ||||||||||||||||||||||
> If you configure your Container registry to use **[RBAC Registry + ABAC Repository Permissions](/azure/container-registry/container-registry-rbac-abac-repository-permissions?tabs=azure-portal)** | ||||||||||||||||||||||
> | ||||||||||||||||||||||
>  | ||||||||||||||||||||||
> | ||||||||||||||||||||||
>In this case, some existing role assignments aren't honored or will have different effects, because a different set of ACR built-in roles apply to ABAC-enabled registries. | ||||||||||||||||||||||
Comment on lines
+119
to
+123
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The IMPORTANT callout block has an incomplete sentence structure. Line 119 starts with 'If you configure...' but doesn't have a complete conditional statement. Consider restructuring to either complete the conditional or change to a declarative statement like 'When you configure your Container registry to use..., the following considerations apply:'
Suggested change
Copilot uses AI. Check for mistakes. Positive FeedbackNegative Feedback |
||||||||||||||||||||||
> | ||||||||||||||||||||||
> For example, the **AcrPull**, **AcrPush**, and **AcrDelete** roles aren't honored in an ABAC-enabled registry. | ||||||||||||||||||||||
> Instead, in ABAC-enabled registries, use the `Container Registry Repository Reader`, `Container Registry Repository Writer`, and `Container Registry Repository Contributor` roles to grant either registry-wide or repository-specific image permissions. | ||||||||||||||||||||||
> | ||||||||||||||||||||||
> Ensure that the SAI or the UAI of your endpoint has the **Container Registry Repository Contributor** role assigned on the Container registry. | ||||||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [nitpick] The role names should be consistently formatted. The three role names are enclosed in backticks while the role name in line 128 uses bold formatting. Consider using consistent formatting (either all backticks or all bold) for better readability.
Suggested change
Copilot uses AI. Check for mistakes. Positive FeedbackNegative Feedback |
||||||||||||||||||||||
|
||||||||||||||||||||||
### Automatic role assignment for endpoint identity | ||||||||||||||||||||||
|
||||||||||||||||||||||
If the endpoint identity is a SAI, the following roles are assigned to the endpoint identity for convenience. | ||||||||||||||||||||||
|
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 image doesn't exist. Please replace it with a valid one.
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.
@dem108 took this from https://learn.microsoft.com/en-us/azure/container-registry/media/container-registry-rbac-abac-repository-permissions/rbac-abac-repository-permissions-02-update-registry.png can you please help with the relative path for this image
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.
@sanjayananthamurthy - The image is in a different repository, and it would need to be moved to azure-ai-docs if you want to use it here. However, since you're already referencing the article that includes the image, you might want to consider omitting it here.