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
There already is `envFromSecret` and `extraEnvSecrets`, so I made
`envFromConfigMap` behave like `envFromSecret` and added
`extraEnvConfigMaps` to replace it.
This pattern should make the intended use of the values clearer.
Copy file name to clipboardExpand all lines: charts/cluster-autoscaler/README.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,10 @@ Releases of the chart from `9.0.0` onwards return the naming of the chart to `cl
46
46
47
47
To migrate from a 1.X release of the chart to a `9.0.0` or later release, you should first uninstall your `1.X` install of the `cluster-autoscaler-chart` chart, before performing the installation of the new `cluster-autoscaler` chart.
48
48
49
+
## Migration from 9.0 to 9.1
50
+
51
+
Starting from `9.1.0` the `envFromConfigMap` value is expected to contain the name of a ConfigMap that is used as ref for `envFrom`, similar to `envFromSecret`. If you want to keep the previous behaviour of `envFromConfigMap` you must rename it to `extraEnvConfigMaps`.
52
+
49
53
## Installing the Chart
50
54
51
55
**By default, no deployment is created and nothing will autoscale**.
@@ -343,9 +347,13 @@ Though enough for the majority of installations, the default PodSecurityPolicy _
343
347
| cloudProvider | string |`"aws"`| The cloud provider where the autoscaler runs. Currently only `gce`, `aws`, `azure` and `magnum` are supported. `aws` supported for AWS. `gce` for GCE. `azure` for Azure AKS. `magnum` for OpenStack Magnum. |
344
348
| containerSecurityContext | object |`{}`|[Security context for container](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/)|
345
349
| dnsPolicy | string |`"ClusterFirst"`| Defaults to `ClusterFirst`. Valid values are: `ClusterFirstWithHostNet`, `ClusterFirst`, `Default` or `None`. If autoscaler does not depend on cluster DNS, recommended to set this to `Default`. |
350
+
| envFromConfigMap | string |`""`| ConfigMap name to use as envFrom. |
351
+
| envFromSecret | string |`""`| Secret name to use as envFrom. |
346
352
| expanderPriorities | object |`{}`| The expanderPriorities is used if `extraArgs.expander` is set to `priority` and expanderPriorities is also set with the priorities. If `extraArgs.expander` is set to `priority`, then expanderPriorities is used to define cluster-autoscaler-priority-expander priorities. See: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/expander/priority/readme.md|
Copy file name to clipboardExpand all lines: charts/cluster-autoscaler/README.md.gotmpl
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,10 @@ Releases of the chart from `9.0.0` onwards return the naming of the chart to `cl
46
46
47
47
To migrate from a 1.X release of the chart to a `9.0.0` or later release, you should first uninstall your `1.X` install of the `cluster-autoscaler-chart` chart, before performing the installation of the new `cluster-autoscaler` chart.
48
48
49
+
## Migration from 9.0 to 9.1
50
+
51
+
Starting from `9.1.0` the `envFromConfigMap` value is expected to contain the name of a ConfigMap that is used as ref for `envFrom`, similar to `envFromSecret`. If you want to keep the previous behaviour of `envFromConfigMap` you must rename it to `extraEnvConfigMaps`.
52
+
49
53
## Installing the Chart
50
54
51
55
**By default, no deployment is created and nothing will autoscale**.
0 commit comments