Skip to content

Commit a6a54e8

Browse files
committed
use backticks to escape braces
Signed-off-by: Fernando Crespo Gravalos <[email protected]>
1 parent 365c3d1 commit a6a54e8

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

charts/cluster-autoscaler/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -183,7 +183,7 @@ $ helm install my-release autoscaler/cluster-autoscaler \
183183

184184
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-`.
185185

186-
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 }}`
186+
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 }}`
187187

188188
In the event you want to explicitly specify MIGs instead of using auto-discovery, set members of the `autoscalingGroups` array directly - e.g.
189189

@@ -334,7 +334,7 @@ Once you have the IAM role configured, you would then need to `--set rbac.servic
334334
rbac:
335335
serviceAccount:
336336
annotations:
337-
eks.amazonaws.com/role-arn: "\{\{ .Values.aws.myroleARN }}"
337+
eks.amazonaws.com/role-arn: "{{ .Values.aws.myroleARN }}"
338338
```
339339

340340
### Azure - Using azure workload identity

charts/cluster-autoscaler/README.md.gotmpl

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -183,7 +183,7 @@ $ helm install my-release autoscaler/cluster-autoscaler \
183183

184184
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-`.
185185

186-
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 }}`
186+
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 }}`}}`
187187

188188
In the event you want to explicitly specify MIGs instead of using auto-discovery, set members of the `autoscalingGroups` array directly - e.g.
189189

@@ -335,7 +335,7 @@ Once you have the IAM role configured, you would then need to `--set rbac.servic
335335
rbac:
336336
serviceAccount:
337337
annotations:
338-
eks.amazonaws.com/role-arn: "\{\{ .Values.aws.myroleARN }}"
338+
eks.amazonaws.com/role-arn: "{{`{{ .Values.aws.myroleARN `}}}}"
339339
```
340340

341341
### Azure - Using azure workload identity

0 commit comments

Comments
 (0)