fix logic error: SetDiscoveryConfig should be called in both local mode and non-local mode #2471
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.



What type of PR is this?
What this PR does / why we need it:
In #2449, SetDiscoveryConfig is modified, in which this function is only called in non-local mode for yurtadm join. as the following figure.
However, when use in local mode, yurtadm also need call SetDiscoveryConfig to configure discovery file, then kubeadm-config contains this discovery to perfom joining a node.
Which issue(s) this PR fixes:
Fixes #2449
Special notes for your reviewer:
Does this PR introduce a user-facing change?
other Note