Skip to content
Snippets Groups Projects
Commit a6a54e88 authored by Fernando Crespo Gravalos's avatar Fernando Crespo Gravalos
Browse files

use backticks to escape braces

parent 365c3d1d
Branches
Tags
No related merge requests found
......@@ -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
......
......@@ -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
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please to comment