Add option way toget rest config of estimator schedule #3689
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.
Get rest config from aggregate apiserver if member cluster kubeconfig not provided.
What type of PR is this?
What this PR does / why we need it:
Get rest config from aggregate apiserver if member cluster kubeconfig not provided. Users may access the karmada control plane in different machine, some may not have member kubeconf exactly, and can also enable estimator across the control plane kubeconf, it's hard for user to manage all member cluster's kubeconf.
Which issue(s) this PR fixes:
Fixes #3687
Special notes for your reviewer:
NONE
Does this PR introduce a user-facing change?: