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
Copy file name to clipboardExpand all lines: charts/cluster-autoscaler/README.md
+30-1Lines changed: 30 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -250,6 +250,34 @@ In order to accomplish this, you will first need to create a new IAM role with t
250
250
251
251
Once you have the IAM role configured, you would then need to `--set rbac.serviceAccount.annotations."eks\.amazonaws\.com/role-arn"=arn:aws:iam::123456789012:role/MyRoleName` when installing.
252
252
253
+
### Azure - Using azure workload identity
254
+
255
+
You can use the project [Azure workload identity](https://github.com/Azure/azure-workload-identity), to automatically configure the correct setup for your pods to used federated identity with Azure.
256
+
You can also set the correct settings yourself instead of relying on this project.
257
+
For example the following configuration will configure the Autoscaler to use your federated identity:
The chart will succeed even if the container arguments are incorrect. A few minutes after starting
@@ -303,7 +331,8 @@ Though enough for the majority of installations, the default PodSecurityPolicy _
303
331
| azureResourceGroup | string | `""` | Azure resource group that the cluster is located. Required if `cloudProvider=azure` |
304
332
| azureSubscriptionID | string | `""` | Azure subscription where the resources are located. Required if `cloudProvider=azure` |
305
333
| azureTenantID | string | `""` | Azure tenant where the resources are located. Required if `cloudProvider=azure` |
306
-
| azureUseManagedIdentityExtension | bool |`false`| Whether to use Azure's managed identity extension for credentials. If using MSI, ensure subscription ID, resource group, and azure AKS cluster name are set. |
334
+
| azureUseManagedIdentityExtension | bool | `false` | Whether to use Azure's managed identity extension for credentials. If using MSI, ensure subscription ID, resource group, and azure AKS cluster name are set. You can only use one authentication method at a time, either azureUseWorkloadIdentityExtension or azureUseManagedIdentityExtension should be set. |
335
+
| azureUseWorkloadIdentityExtension | bool | `false` | Whether to use Azure's workload identity extension for credentials. See the project here: https://github.com/Azure/azure-workload-identity for more details. You can only use one authentication method at a time, either azureUseWorkloadIdentityExtension or azureUseManagedIdentityExtension should be set. |
| cloudProvider | string | `"aws"` | The cloud provider where the autoscaler runs. Currently only `gce`, `aws`, `azure`, `magnum` and `clusterapi` are supported. `aws` supported for AWS. `gce` for GCE. `azure` for Azure AKS. `magnum` for OpenStack Magnum, `clusterapi` for Cluster API. |
Copy file name to clipboardExpand all lines: charts/cluster-autoscaler/README.md.gotmpl
+28Lines changed: 28 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -251,6 +251,34 @@ In order to accomplish this, you will first need to create a new IAM role with t
251
251
252
252
Once you have the IAM role configured, you would then need to `--set rbac.serviceAccount.annotations."eks\.amazonaws\.com/role-arn"=arn:aws:iam::123456789012:role/MyRoleName` when installing.
253
253
254
+
### Azure - Using azure workload identity
255
+
256
+
You can use the project [Azure workload identity](https://github.com/Azure/azure-workload-identity), to automatically configure the correct setup for your pods to used federated identity with Azure.
257
+
You can also set the correct settings yourself instead of relying on this project.
258
+
For example the following configuration will configure the Autoscaler to use your federated identity:
Copy file name to clipboardExpand all lines: charts/cluster-autoscaler/values.yaml
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,10 @@ azureClusterName: ""
95
95
# Required if `cloudProvider=azure`
96
96
azureNodeResourceGroup: ""
97
97
98
-
# azureUseManagedIdentityExtension -- Whether to use Azure's managed identity extension for credentials. If using MSI, ensure subscription ID, resource group, and azure AKS cluster name are set.
98
+
# azureUseWorkloadIdentityExtension -- Whether to use Azure's workload identity extension for credentials. See the project here: https://github.com/Azure/azure-workload-identity for more details. You can only use one authentication method at a time, either azureUseWorkloadIdentityExtension or azureUseManagedIdentityExtension should be set.
99
+
azureUseWorkloadIdentityExtension: false
100
+
101
+
# azureUseManagedIdentityExtension -- Whether to use Azure's managed identity extension for credentials. If using MSI, ensure subscription ID, resource group, and azure AKS cluster name are set. You can only use one authentication method at a time, either azureUseWorkloadIdentityExtension or azureUseManagedIdentityExtension should be set.
99
102
azureUseManagedIdentityExtension: false
100
103
101
104
# magnumClusterName -- Cluster name or ID in Magnum.
0 commit comments