kubernetes
/
autoscaler
mirror of https://github.com/kubernetes/autoscaler.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

use backticks to escape braces 

Signed-off-by: Fernando Crespo Gravalos <fcrespo@fastly.com>
This commit is contained in:
Fernando Crespo Gravalos 2025-03-31 07:02:34 +02:00
parent 365c3d1d0c
commit a6a54e8806
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
charts/cluster-autoscaler/README.md
View File

@ -183,7 +183,7 @@ $ helm install my-release autoscaler/cluster-autoscaler \
Note that `your-ig-prefix` should be a _prefix_ matching one or more MIGs, and _not_ the full name of the MIG. For example, to match multiple instance groups - `k8s-node-group-a-standard`, `k8s-node-group-b-gpu`, you would use a prefix of `k8s-node-group-`.
Prefixes will be rendered using `tpl` function so you can use any value of your choice if that's a valid prefix. For instance (ignore escaping characters): `gke-\{\{ .Values.autoDiscovery.clusterName }}`
Prefixes will be rendered using `tpl` function so you can use any value of your choice if that's a valid prefix. For instance (ignore escaping characters): `gke-{{ .Values.autoDiscovery.clusterName }}`
In the event you want to explicitly specify MIGs instead of using auto-discovery, set members of the `autoscalingGroups` array directly - e.g.
@ -334,7 +334,7 @@ Once you have the IAM role configured, you would then need to `--set rbac.servic
rbac:
serviceAccount:
annotations:
eks.amazonaws.com/role-arn: "\{\{ .Values.aws.myroleARN }}"
eks.amazonaws.com/role-arn: "{{ .Values.aws.myroleARN }}"
```
### Azure - Using azure workload identity

4
charts/cluster-autoscaler/README.md.gotmpl
View File

@ -183,7 +183,7 @@ $ helm install my-release autoscaler/cluster-autoscaler \
Note that `your-ig-prefix` should be a _prefix_ matching one or more MIGs, and _not_ the full name of the MIG. For example, to match multiple instance groups - `k8s-node-group-a-standard`, `k8s-node-group-b-gpu`, you would use a prefix of `k8s-node-group-`.
Prefixes will be rendered using `tpl` function so you can use any value of your choice if that's a valid prefix. For instance (ignore escaping characters): `gke-\{\{ .Values.autoDiscovery.clusterName }}`
Prefixes will be rendered using `tpl` function so you can use any value of your choice if that's a valid prefix. For instance (ignore escaping characters): `gke-{{`{{ .Values.autoDiscovery.clusterName }}`}}`
In the event you want to explicitly specify MIGs instead of using auto-discovery, set members of the `autoscalingGroups` array directly - e.g.
@ -335,7 +335,7 @@ Once you have the IAM role configured, you would then need to `--set rbac.servic
rbac:
serviceAccount:
annotations:
eks.amazonaws.com/role-arn: "\{\{ .Values.aws.myroleARN }}"
eks.amazonaws.com/role-arn: "{{`{{ .Values.aws.myroleARN `}}}}"
```
### Azure - Using azure workload identity