-
Notifications
You must be signed in to change notification settings - Fork 97
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
Categorize certain aws-route53 errors as configuration problems #398
Categorize certain aws-route53 errors as configuration problems #398
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.
/lgtm
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.
Looks good to me. Just two missing doc strings.
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 apart from the nits mentioned by @dkistner
I guess we still
/hold
as there is the ongoing release validation? cc @ialidzhikov
I think it should be fine to include this one as it affects only the dnsrecord controller which is still not heavily used. /unhold |
/milestone v1.28 |
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
How to categorize this PR?
/area ops-productivity
/kind enhancement
/platform aws
What this PR does / why we need it:
Categorizes certain aws-route53 errors as configuration problems as suggested in gardener/gardener#4294.
Which issue(s) this PR fixes:
Fixes gardener/gardener#4294
Special notes for your reviewer:
Release note: