-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-2.12] Add MCOA status for CRD dependencies #1564
Conversation
Signed-off-by: Periklis Tsirakidis <[email protected]>
Signed-off-by: Periklis Tsirakidis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. One question, this means we lock users into always having a CRD present if the capability is enabled correct?
My question is mostly around a potentially application/restoration of the CRD when the CRD might be absent, but the MCOA reconciliation loop will error as they are not present. I suspect this is just an acceptable edge case at this point, and it will pick it up in the next reconciliation loop.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: moadz, periklis The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
Signed-off-by: Periklis Tsirakidis <[email protected]>
Quality Gate failedFailed conditions |
/test test-unit |
@periklis: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
key := client.ObjectKey{Name: crdName} | ||
|
||
err := c.Get(context.TODO(), key, crd) | ||
if client.IgnoreAlreadyExists(err) != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: why are we ignoring for AlreadyExists here?
} | ||
|
||
if len(missing) == 0 { | ||
removeStatusCondition(conds, reasonMCOADegraded) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't work because this function works on Type
and not Reason
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
The following PR is an amendment/extention to #1470 to improve the user experience when a user decides to use the new
capabilities
spec and in turn MCOA. Currently the MCOA internal reconciliation loop depends on a set of CustomResourceDefinitions (CRD) owned by other operator dependecies (i.e.cluster-logging-operator
,opentelemetrycollector-operator
). The underlying implementation checks if the CRDs exist and actually serve the required CRD versions. If any is missing the MCO status shows theMCOADegradedCondition
, e.g.:cc @JoaoBraveCoding @moadz @pavolloffay