You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This authentication method can be specificaly used by setting the `AZURE_AUTH_METHOD` environment variable to `env`.
135
+
109
136
### Workload identity
110
137
111
-
#### Azure Managed Identity
138
+
Workload identity allows workloads running Azure Kubernetes Services (AKS) clusters to authenticate as an Azure AD application identity using federated credentials.
139
+
140
+
This must be configured in kubernetes workload deployment in one hand and on the Azure AD application registration in the other hand.
141
+
142
+
Here is a summary of the steps to follow to use it :
143
+
* create a `ServiceAccount` resource, add following annotations to reference the targeted Azure AD application registration : `azure.workload.identity/client-id` and `azure.workload.identity/tenant-id`.
144
+
* on the `Deployment` resource you must reference the previous `ServiceAccount` and add the following label : `azure.workload.identity/use: "true"`.
145
+
* create a fedreated credentials of type `Kubernetes accessing Azure resources`, add the cluster issuer URL and add the namespace and name of your kubernetes service account.
146
+
147
+
Link :
148
+
-[Azure AD Workload identity](https://azure.github.io/azure-workload-identity/docs/topics/service-account-labels-and-annotations.html)
149
+
150
+
This authentication method can be specificaly used by setting the `AZURE_AUTH_METHOD` environment variable to `wli`.
151
+
152
+
### Azure Managed Identity
153
+
154
+
#### Azure Managed Identity (with Azure workload)
112
155
113
156
The Azure Managed Identity service allows linking Azure AD identities to Azure resources, without needing to manually manage client IDs and secrets.
Workload identity allows workloads running Azure Kubernetes Services (AKS) clusters to authenticate as an Azure AD application identity using federated credentials.
200
+
A timeout wrapper is configured for this authentication method.
201
+
The duraction can be configured by setting the `AZURE_AUTH_MSI_TIMEOUT`.
202
+
The default timeout is 2 seconds.
203
+
This authentication method can be specificaly used by setting the `AZURE_AUTH_METHOD` environment variable to `msi`.
155
204
156
-
This must be configured in kubernetes workload deployment in one hand and on the Azure AD application registration in the other hand.
205
+
### Azure CLI
157
206
158
-
Here is a summary of the steps to follow to use it :
159
-
* create a `ServiceAccount` resource, add following annotations to reference the targeted Azure AD application registration : `azure.workload.identity/client-id` and `azure.workload.identity/tenant-id`.
160
-
* on the `Deployment` resource you must reference the previous `ServiceAccount` and add the following label : `azure.workload.identity/use: "true"`.
161
-
* create a fedreated credentials of type `Kubernetes accessing Azure resources`, add the cluster issuer URL and add the namespace and name of your kubernetes service account.
207
+
The Azure CLI is a command-line tool provided by Microsoft to interact with Azure resources.
208
+
It provides an easy way to authenticate by simply running `az login` command.
209
+
The generated token will be cached by default in the `~/.azure` folder.
162
210
163
-
Link :
164
-
-[Azure AD Workload identity](https://azure.github.io/azure-workload-identity/docs/topics/service-account-labels-and-annotations.html)
211
+
This authentication method can be specificaly used by setting the `AZURE_AUTH_METHOD` environment variable to `cli`.
0 commit comments