karmada
karmada copied to clipboard
karmada-io
Scheduler always connect karmada-scheduler-estimator-cluster service while karmada system is deployed by `karmada-init`
What happened:
Scheduler always connect karmada-scheduler-estimator-cluster service while karmada system is deployed by karmada-init
Scheduler log error continuously
What you expected to happen:
Scheduler log normally
@RainbowMango @lonelyCZ
Do you think we should set the option enable-scheduler-estimator=false in karmada-init becasue the component karmada-scheduler-estimator is not included.
And In future we can deploy or enable the optional compents in karmadactl
How to reproduce it (as minimally and precisely as possible):
use karmada-init to deploy a karmada-system
Anything else we need to know?:
Environment:
- Karmada version:
- kubectl-karmada or karmadactl version (the result of
kubectl-karmada versionorkarmadactl version): - Others:
This should be in order to enable the scheduler-estimator at any time, otherwise we need to restart the karmada-scheduler when we deploy the estimator for the member cluster.
Perhaps, this polling is more frequent, is there a way to automatically detect, automatic sleep.
We cannot detect existence of karmada-scheduler-estimator by Service.
When deploy in Host Kubernetes Cluster, there is a Service named karmada-scheduler-estimator-{{MEMBER_CLUSTER_NAME}} for routing info. But this Service is inside Host Kubernetes Cluster, and karmada-scheduler only connects to kube-apiserver for Karmada itself.
