external: honour support of cluster-name legacy flag #13540
Merged
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
we have changed the --cluster-name flag to --k8s-cluster-name but to support automation while upgrade we should support the legacy flag Signed-off-by: parth-gr <partharora1010@gmail.com>
parth-gr
force-pushed
the
external-cluster-flag
branch
from
7a1a405
to
8e4ec01
Compare
travisn
approved these changes
Jan 9, 2024
travisn
added a commit
that referenced
this pull request
Jan 11, 2024
external: honour support of cluster-name legacy flag (backport #13540)
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.
we have changed the --cluster-name flag to --k8s-cluster-name but to support automation while upgrade we should support the legacy flag
Checklist: