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
The upgrade-job, as of 2.7.0 reuses all of the existing helm values from the source chart. The removal of the parameter from the values.yaml would mean that during upgrade that value has to be forcibly removed when moving to 2.7.0+ versions. This needs to be handled somehow.
If there is no new design changes to upgrade, a new entry to the helm::values.rs module is required which explicitly removes the value from the values set. This might also be required even if helm's --reset-then-reuse-values flag is used, as previous upgrade-jobs would have used the -f values.yaml option during upgrade and would have explicitly set ALL of the source chart's values (and they would be now visible on helm get values output).
The text was updated successfully, but these errors were encountered:
Fixesopenebs/mayastor#1735
This removes the helm value for the key etcd.initialClusterState for all
versions greater than or equal to 2.0.0-rc.0 and less than 2.7.3.
Signed-off-by: Niladri Halder <[email protected]>
Fixesopenebs/mayastor#1735
This removes the helm value for the key etcd.initialClusterState for all
versions greater than or equal to 2.0.0-rc.0 and less than 2.7.3.
Signed-off-by: Niladri Halder <[email protected]>
595: fix(upgrade): remove etcd.initialClusterState from helm values r=niladrih a=niladrih
Fixesopenebs/mayastor#1735
This removes the helm value for the key etcd.initialClusterState for all versions greater than or equal to 2.0.0-rc.0 and less than 2.7.3.
Co-authored-by: Niladri Halder <[email protected]>
niladrih
added a commit
to openebs/mayastor-extensions
that referenced
this issue
Jan 8, 2025
Fixesopenebs/mayastor#1735
This removes the helm value for the key etcd.initialClusterState for all
versions greater than or equal to 2.0.0-rc.0 and less than 2.7.3.
Signed-off-by: Niladri Halder <[email protected]>
Ref: openebs/mayastor-extensions#536
The upgrade-job, as of 2.7.0 reuses all of the existing helm values from the source chart. The removal of the parameter from the values.yaml would mean that during upgrade that value has to be forcibly removed when moving to 2.7.0+ versions. This needs to be handled somehow.
If there is no new design changes to upgrade, a new entry to the helm::values.rs module is required which explicitly removes the value from the values set. This might also be required even if helm's
--reset-then-reuse-values
flag is used, as previous upgrade-jobs would have used the-f values.yaml
option during upgrade and would have explicitly set ALL of the source chart's values (and they would be now visible onhelm get values
output).The text was updated successfully, but these errors were encountered: