Closed JackZxj closed 5 months ago
Attention: 192 lines
in your changes are missing coverage. Please review.
Comparison is base (
cef22e2
) 32.99% compared to head (f0394c7
) 33.06%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Two new parameters have been added to support katalyst:
--enable-katalyst-support=true
Enable katalyst support in the cluster controller and scheduler. Enabling this, cluster controller will collect katalyst CNR resource into FederatedCluster if katalyst plugin was enabled in its annotations, and the scheduler will enable KatalystResourcesExist filter (it will filter out clusters without katalyst resources) and support split replicas by katalyst resources (Split priority: GPU > katalyst cpu > cpu).--cluster-health-check-period=30s
The period of health check for member clusters. The minimum value is 15s.After enabling katalyst support, if any member cluster supports katalyst, you can add the following annotation to it's fcluster to collect CNR information:
kubectl annotate fcluster kubeadmiral-member-1 kubeadmiral.io/cluster-resource-plugins="[\"node.katalyst.kubewharf.io\"]" --overwrite