Report reconciliation errors as part of the component' status (pt1) #1684
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This commit introduces some enhancement to what and how components are
reporting theirs status by:
Ready
top-level condition which summarizes more detailedconditions
ProvisioningSucceeded
condition that reports anyprovisioning error, i.e. a deployment fails to be provisioned because
of any invalid fields, some pre-requisites are not met
Note
in the case we want a condition to be set to
False
, but that should not affect the top level condition, it is possible to set theseverity
field asInfo
(the default isError
and it is being represented by an empty value):If needed, additional conditions can be added by individual component or
services:
To help managing conditions, a
conditions.Manager
type has beeninrtoduced, largely inspired by Knative's conditions set code [1], but
improved to handle our specific use cases.
[1] https://github.com/knative/pkg/blob/main/apis/condition_set.go
https://issues.redhat.com/browse/RHOAIENG-18216
How Has This Been Tested?
Screenshot or short clip
Merge criteria