fix logic error: SetDiscoveryConfig should be called in both local mode and non-local mode#2471
fix logic error: SetDiscoveryConfig should be called in both local mode and non-local mode#2471huangchenzhao wants to merge 2 commits intoopenyurtio:masterfrom
Conversation
…de and non-local mode
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2471 +/- ##
==========================================
+ Coverage 42.96% 43.09% +0.12%
==========================================
Files 396 396
Lines 26298 26337 +39
==========================================
+ Hits 11300 11350 +50
+ Misses 13941 13930 -11
Partials 1057 1057
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…ty and add prepare_test.go for testing
1fbdf91 to
e9fcfa7
Compare
|
|
@zyjhtangtang This PR is originally for fixing the calling logic of function |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |



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