-
Notifications
You must be signed in to change notification settings - Fork 461
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
Ensure backup entry name is generated only once using non-empty strings #4454
Ensure backup entry name is generated only once using non-empty strings #4454
Conversation
/invite @timuthy @plkokanov @ialidzhikov |
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 @stoyanr for the changes! 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.
/lgtm
Thank you very much @stoyanr
/needs cherry-pick |
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!
Just some suggestions from my side.
And please, add a release note.
c84c05b
to
756af3d
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 alot for the PR!
/lgtm
…upstream-release-v1.26 [release-v1.26] Automated cherry pick of #4454: Ensure backup entry name is generated only once using non-empty strings
…upstream-release-v1.28 [release-v1.28] Automated cherry pick of #4454: Ensure backup entry name is generated only once using non-empty strings
…upstream-release-v1.27 [release-v1.27] Automated cherry pick of #4454: Ensure backup entry name is generated only once using non-empty strings
How to categorize this PR?
/area control-plane
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
This is intended as a quick fix to a recently observed issue that is caused by generating a backup entry name
--
when deployingEtcd
resources. It does not fix the root cause of the issue (likely some kind of data race), just aims to prevent it from happening by ensuring the backup entry name is generated correctly.See gardener/gardener-extension-provider-azure#328 (comment).
Release note: