Given it is possible for a custom resource to be in error / failed state while a new reconcile process is ongoing, it is unnecessary to mark the status of previous Failure conditions to False while the reconcile loop is still running.
The failure condition will be removed when the custom resource is successfully deployed as it works today.
Motivation for the change:
The failure conditions have timestamps and are accurate as at the time of reporting. Therefore, it would be unnecessary and misleading to set the failure condition status to False before the custom resource is successfully deployed.
Checklist
If the pull request includes user-facing changes, extra documentation is required:
Description of the change:
Given it is possible for a custom resource to be in error / failed state while a new reconcile process is ongoing, it is unnecessary to mark the status of previous Failure conditions to
Falsewhile the reconcile loop is still running.The failure condition will be removed when the custom resource is successfully deployed as it works today.
Motivation for the change:
The failure conditions have timestamps and are accurate as at the time of reporting. Therefore, it would be unnecessary and misleading to set the failure condition status to
Falsebefore the custom resource is successfully deployed.Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments(seechangelog/fragments/00-template.yaml)website/content/en/docs