John Garbutt
d60ae3f89c
By default, since release 0.8.0 of capi-helm, it has been defaulting to WaitForFirstConsumer for additional storage classes. https://github.com/azimuth-cloud/capi-helm-charts/commit/854172966653138a60c329215fe9bb18726353e6 Note, if you are upgrading from an older version, we hit some upgrade issues due to immutable storage classes being unable to be updated. As a work around, we are actully making use of the existing config, to keep the behaviour the same as the current release of the capi-helm-charts. But those using older versions, before 0.8.0, may need to change the configuration to match their existing choices, ahead of their upgrade. Change-Id: If90e0143f56ee378f5401b01623c159836fef29c Signed-off-by: John Garbutt <john.garbutt@stackhpc.com>
12 lines
598 B
YAML
12 lines
598 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
csi_cinder_volume_binding_mode previously had no effect. If you use
|
|
capi-helm-charts<0.8.0 then you would have set it to Immediate and since
|
|
0.8.0 it has defaulted to WaitForFirstConsumer. The configuration is now
|
|
being used, and we have set the default to match the new versions of the
|
|
capi-helm-charts. However, if you have older clusters using a template
|
|
with a very old capi-helm-chart, then really you need to keep the older
|
|
default, to avoid a breakage on upgrade. This is specifically because
|
|
the storage class, once created, is immutable.
|