|
|
@@ -9,7 +9,6 @@ The token is generated for a particular ACR registry defined in `spec.registry`.
|
|
|
| username | username for the `docker login` command |
|
|
|
| password | password for the `docker login` command |
|
|
|
|
|
|
-
|
|
|
## Authentication
|
|
|
|
|
|
You must choose one out of three authentication mechanisms:
|
|
|
@@ -21,6 +20,8 @@ You must choose one out of three authentication mechanisms:
|
|
|
The generated token will inherit the permissions from the assigned policy. I.e. when you assign a read-only policy all generated tokens will be read-only.
|
|
|
You **must** [assign a Azure RBAC role](https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-steps), such as `AcrPush` or `AcrPull` to the service principal or managed identity in order to be able to authenticate with the Azure container registry API.
|
|
|
|
|
|
+You can also use a kubelet managed identity with the default `AcrPull` role to authenticate to the integrated Azure Container Registry.
|
|
|
+
|
|
|
You can scope tokens to a particular repository using `spec.scope`.
|
|
|
|
|
|
## Scope
|
|
|
@@ -49,6 +50,13 @@ repository:my-repository:pull
|
|
|
```
|
|
|
|
|
|
Example `ExternalSecret` that references the ACR generator:
|
|
|
+
|
|
|
```yaml
|
|
|
{% include 'generator-acr-example.yaml' %}
|
|
|
```
|
|
|
+
|
|
|
+Example using AKS kubelet managed identity to create [Argo CD helm chart repository](https://argo-cd.readthedocs.io/en/latest/operator-manual/declarative-setup/#helm-chart-repositories) secret:
|
|
|
+
|
|
|
+```yaml
|
|
|
+{% include 'generator-acr-argocd-helm-repo.yaml' %}
|
|
|
+```
|