From 8b31ea01404c2b0494f0e598a12b112dd6e42f44 Mon Sep 17 00:00:00 2001
From: Jack Francis <jackfrancis@gmail.com>
Date: Fri, 28 Mar 2025 15:18:30 -0700
Subject: [PATCH] helm: backtick to escape braces
Signed-off-by: Jack Francis <jackfrancis@gmail.com>
---
charts/cluster-autoscaler/Chart.yaml | 2 +-
charts/cluster-autoscaler/README.md | 2 +-
charts/cluster-autoscaler/README.md.gotmpl | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/charts/cluster-autoscaler/Chart.yaml b/charts/cluster-autoscaler/Chart.yaml
index 0e1a5a99d8..5b2c25dc40 100644
--- a/charts/cluster-autoscaler/Chart.yaml
+++ b/charts/cluster-autoscaler/Chart.yaml
@@ -11,4 +11,4 @@ name: cluster-autoscaler
sources:
- https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler
type: application
-version: 9.46.4
+version: 9.46.5
diff --git a/charts/cluster-autoscaler/README.md b/charts/cluster-autoscaler/README.md
index 420da9d18d..ea8b6bd0b2 100644
--- a/charts/cluster-autoscaler/README.md
+++ b/charts/cluster-autoscaler/README.md
@@ -79,7 +79,7 @@ To create a valid configuration, follow instructions for your cloud provider:
### Templating the autoDiscovery.clusterName
-The cluster name can be templated in the `autoDiscovery.clusterName` variable. This is useful when the cluster name is dynamically generated based on other values coming from external systems like Argo CD or Flux. This also allows you to use global Helm values to set the cluster name, e.g., `autoDiscovery.clusterName=\{\{ .Values.global.clusterName }}`, so that you don't need to set it in more than 1 location in the values file.
+The cluster name can be templated in the `autoDiscovery.clusterName` variable. This is useful when the cluster name is dynamically generated based on other values coming from external systems like Argo CD or Flux. This also allows you to use global Helm values to set the cluster name, e.g., `autoDiscovery.clusterName={{ .Values.global.clusterName }}`, so that you don't need to set it in more than 1 location in the values file.
### AWS - Using auto-discovery of tagged instance groups
diff --git a/charts/cluster-autoscaler/README.md.gotmpl b/charts/cluster-autoscaler/README.md.gotmpl
index 786dbec1dc..55995b1988 100644
--- a/charts/cluster-autoscaler/README.md.gotmpl
+++ b/charts/cluster-autoscaler/README.md.gotmpl
@@ -79,7 +79,7 @@ To create a valid configuration, follow instructions for your cloud provider:
### Templating the autoDiscovery.clusterName
-The cluster name can be templated in the `autoDiscovery.clusterName` variable. This is useful when the cluster name is dynamically generated based on other values coming from external systems like Argo CD or Flux. This also allows you to use global Helm values to set the cluster name, e.g., `autoDiscovery.clusterName=\{\{ .Values.global.clusterName }}`, so that you don't need to set it in more than 1 location in the values file.
+The cluster name can be templated in the `autoDiscovery.clusterName` variable. This is useful when the cluster name is dynamically generated based on other values coming from external systems like Argo CD or Flux. This also allows you to use global Helm values to set the cluster name, e.g., `autoDiscovery.clusterName={{`{{ .Values.global.clusterName }}`}}`, so that you don't need to set it in more than 1 location in the values file.
### AWS - Using auto-discovery of tagged instance groups
--
GitLab