-
Notifications
You must be signed in to change notification settings - Fork 900
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
k8s API sets the default value of claim's spec.compositeDeletePolicy
field
#4768
k8s API sets the default value of claim's spec.compositeDeletePolicy
field
#4768
Conversation
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 is so much better than my original implementation - great work!
It LGTM but I'll let someone with more go experience approve it.
2f2c29f
to
ac3f3cc
Compare
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! I like a mostly red diff, nice work.
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.
one small nit, otherwise LGTM! thanks @pedjak 🎉
…` field * claim CRD contains now the default value for `.spec.compositeDeletePolicy` field copied from XRD `spec.defaultCompositeDeletePolicy`. If not specified at claim, it will be set by k8s API * claim controller does not set the value for `spec.compositeDeletePolicy`, leading to one less claim update, and hence one less no-op reconcile loop * added unit and e2e tests * removed `APIDefaultSelector` as unneeded Signed-off-by: Predrag Knezevic <predrag.knezevic@upbound.io>
ac3f3cc
to
ca10547
Compare
Description of your changes
.spec.compositeDeletePolicy
fieldcopied from XRD
spec.defaultCompositeDeletePolicy
. If not specified at claim,it will be set by k8s API
spec.compositeDeletePolicy
,leading to one less claim update, and hence one less no-op reconcile loop
APIDefaultSelector
as unneededFixes #4691
I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR, if necessary.