-
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?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -23,6 +23,32 @@ | |||||
clusterv1 "sigs.k8s.io/cluster-api/api/v1beta1" | ||||||
) | ||||||
|
||||||
// ClusterResourceSet's ResourcesApplied condition and corresponding reasons that will be used in v1Beta2 API version. | ||||||
const ( | ||||||
// ResourcesAppliedV1beta2Condition surfaces wether the resources in the ClusterResourceSet are applied to all matching clusters. | ||||||
// This indicates all resources exist, and no errors during applying them to all clusters. | ||||||
ResourcesAppliedV1beta2Condition = "ResourcesApplied" | ||||||
|
||||||
// ResourcesAppliedV1beta2Reason is the reason used when all resources in the ClusterResourceSet object got applied | ||||||
// to all matching clusters. | ||||||
ResourcesAppliedV1beta2Reason = "Applied" | ||||||
|
||||||
// ResourcesAppliedApplyFailedV1beta2Reason is the reason used when applying at least one of the resources to one of the matching clusters failed. | ||||||
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 commentThe 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. |
||||||
|
||||||
// ResourcesAppliedClusterMatchFailedV1beta2Reason is the reason used on failure getting clusters that match the clusterSelector. | ||||||
ResourcesAppliedClusterMatchFailedV1beta2Reason = "ClusterMatchFailed" | ||||||
|
||||||
// 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 commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
ResourcesAppliedWrongSecretTypeV1beta2Reason = "WrongSecretType" | ||||||
) | ||||||
|
||||||
const ( | ||||||
// ClusterResourceSetSecretType is the only accepted type of secret in resources. | ||||||
ClusterResourceSetSecretType corev1.SecretType = "addons.cluster.x-k8s.io/resource-set" //nolint:gosec | ||||||
|
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?