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
For rolling upgrades/updates we'll need to have multiple instances of Ember-CSI running against the same backend, so we cannot have a fixed name for the StatefulSet and the DaemonSet of each backend, as that would create a conflict in Kubernetes.
The name could either use the hash of the image that's going to be used, some metadata from the image, or the vendor_version that will be reported by Ember-CSI once it has a finer grained vendor_version (embercsi/ember-csi#108).
The text was updated successfully, but these errors were encountered:
For rolling upgrades/updates we'll need to have multiple instances of Ember-CSI running against the same backend, so we cannot have a fixed name for the
StatefulSet
and theDaemonSet
of each backend, as that would create a conflict in Kubernetes.The name could either use the hash of the image that's going to be used, some metadata from the image, or the
vendor_version
that will be reported by Ember-CSI once it has a finer grainedvendor_version
(embercsi/ember-csi#108).The text was updated successfully, but these errors were encountered: