-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 crs: implement ResourcesApplied v1beta2 condition #11467
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
Thanks for this PR!
We should modify the defer Patch call adding owned condition options
ResourcesAppliedV1beta2Reason = "Applied" | ||
|
||
// ResourcesAppliedApplyFailedV1beta2Reason is the reason used when applying at least one of the resources to one of the matching clusters failed. | ||
ResourcesAppliedApplyFailedV1beta2Reason = "ApplyFailed" |
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.
what about using NotApplied for consistency with other reasons?
// ResourcesAppliedRetrievingResourceFailedV1beta2Reason is the reason used when resources are not successfully retrieved. | ||
ResourcesAppliedRetrievingResourceFailedV1beta2Reason = "RetrievingResourceFailed" | ||
|
||
// ResourcesAppliedWrongSecretTypeV1beta2Reason is the reason used when the the Secret's type in the resource list is not supported. |
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.
// ResourcesAppliedWrongSecretTypeV1beta2Reason is the reason used when the the Secret's type in the resource list is not supported. | |
// ResourcesAppliedWrongSecretTypeV1beta2Reason is the reason used when the Secret's type in the resource list is not supported. |
ResourcesAppliedApplyFailedV1beta2Reason = "ApplyFailed" | ||
|
||
// ResourcesAppliedRemoteClusterClientFailedV1beta2Reason is the reason used on failures during getting the remote cluster client. | ||
ResourcesAppliedRemoteClusterClientFailedV1beta2Reason = "RemoteClusterClientFailed" |
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.
What about using InternalError when the error + eventually changing the message (same for ClusterMatchFailed and RetrievingResourceFailed.
I will keep WrongSecretType as it is because this is a user configuration error
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of #11105
/area conditions