Fix Backup name duplication #6971
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
learner0810
force-pushed
the
fix-backup-name-duplication
branch
from
3b71873 to
f943972
Compare
Signed-off-by: zhongjun.li <zhongjun.li@daocloud.io>
learner0810
force-pushed
the
fix-backup-name-duplication
branch
from
f943972 to
decf20f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for contributing to Velero!
Please add a summary of your change
We installed velero in multiple clusters with identical configurations, and the backups.velero.io name generated by schedules.velero.io was duplicated, so we added a random number to the backups.velero.io name.
Now backups.velero.io name looks like this
schedule-name-20231018165532-6cpgwDoes your change fix a particular issue?
Fixes #(issue)
Please indicate you've done the following:
/kind changelog-not-requiredas a comment on this pull request.site/content/docs/main.