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
During version incompatible upgrades the checkClientCompatibility this reconciler will check if there are any incompatible processes with the new desired version. Currently this is implemented in a sub-optimal way that if the check fails, because at least one process is reported as being incompatible, all the further reconcilers will be skipped. That means this issue must be solved fairly quickly to allow the operator to work properly again.
There are different ways how we could solve this e.g. by doing the actual check of checkClientCompatibility inside the updateStatus reconciler and update the cluster.Status in the FoundationDBCluster resource with the result. Based on that information the updateSidecarVersions could update the sidecars or not. The same check would be needed when the fdb-monitor configuration is created, to make sure that the config is only adjusted when the client compatibility check is fine.
The text was updated successfully, but these errors were encountered:
What would you like to be added/changed?
During version incompatible upgrades the
checkClientCompatibility
this reconciler will check if there are any incompatible processes with the new desired version. Currently this is implemented in a sub-optimal way that if the check fails, because at least one process is reported as being incompatible, all the further reconcilers will be skipped. That means this issue must be solved fairly quickly to allow the operator to work properly again.There are different ways how we could solve this e.g. by doing the actual check of
checkClientCompatibility
inside theupdateStatus
reconciler and update thecluster.Status
in theFoundationDBCluster
resource with the result. Based on that information theupdateSidecarVersions
could update the sidecars or not. The same check would be needed when the fdb-monitor configuration is created, to make sure that the config is only adjusted when the client compatibility check is fine.The text was updated successfully, but these errors were encountered: