BundleDeployment Health: Extend rukpak provisioner to implement BundleDeployment health check #369
Description
Extend rukpak to add a health condition on the status for bundleDeployment CRs based on health statuses of watched/created resources during the installation of the bundleDeployment CR.
The healthy condition will be implemented behind a feature gate.
The Healthy condition should follow from the Installed condition when the Installed condition status is different to “True”:
- If the “Installed” condition status is “False”: the “Healthy” condition status will be set to “False”
- If the “Installed” condition status is “Unknown”: the “Healthy” condition status will be set to “Unknown”
Once the “Installed” condition status is “True”, the “Healthy” condition status will be determined by the healthcheck as described:
Summary of statuses extended with reasons:
| status | reason | message | when |
|---|---|---|---|
| Unknown | ObjectLookupFailure | Contains the error message returned by the kubernetes client when trying to fetch the object. | HealthCheck mechanism is not able to fetch a resource due to an error different to “NotFound” |
| Unknown | InstallationStatusUnknown | “Installation condition is unknown” | The installation condition is Unknown |
| True | Healthy | “All related objects are healthy” | Healthcheck mechanism returns true (defined in #368) |
| False | Unhealthy | Contains statuses of the unhealthy resources ordered lexicographically referencing the failed resource. | The health check mechanism returns false due to some watched resources being unhealthy. (defined in #368) |
| False | InstallationStatusFalse | “Installation condition is false” | The installation condition is False |