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
In a recent sync call on slack, we identified that our current InstalledBundleGetter doesn't return sufficient information to give us a clear picture to determine the appropriate Installed condition state.
After #1296 is fixed, we can implement the following behavior for the Installed condition to adhere to the level-based approach that is expected of Kubernetes controllers:
If we get a nil value and no error from the InstalledBundleGetter - nothing installed (i.e Installed == False)
If we get an error from the InstalledBundleGetter - Installed condition is set to Unknown
If we get a non-nil value from the InstalledBundleGetter and an error happens in a step leading to successful upgrade, Installed condition set to True and Progressing condition contains the upgrade failure
The text was updated successfully, but these errors were encountered:
In a recent sync call on slack, we identified that our current
InstalledBundleGetter
doesn't return sufficient information to give us a clear picture to determine the appropriateInstalled
condition state.After #1296 is fixed, we can implement the following behavior for the
Installed
condition to adhere to the level-based approach that is expected of Kubernetes controllers:nil
value and no error from theInstalledBundleGetter
- nothing installed (i.eInstalled
==False
)InstalledBundleGetter
-Installed
condition is set toUnknown
InstalledBundleGetter
and an error happens in a step leading to successful upgrade,Installed
condition set toTrue
andProgressing
condition contains the upgrade failureThe text was updated successfully, but these errors were encountered: