What's New
Support multi-cluster service discovery
In many cases, a Kubernetes user may want to split their deployments across multiple clusters, but still retain mutual dependencies between workloads running in those clusters.
Users are now able to export and import services between clusters with Multi-Cluster Service API (MCS-API). (@XiShanYongYe-Chang)
Support more precise cluster status management
Besides reporting cluster status, the cluster status controller now also renews the lease. The newly introduced cluster monitor monitors the lease and will mark cluster ready status to unknown in case of cluster status controller not working. (@Garrybest)
Support replica scheduling based on cluster resources
In some scenarios, users want to divide the replicas in a deployment to multiple clusters if a single cluster doesn't have sufficient resources.
Users now able to declare the replica scheduling preference by the new field ReplicaDivisionPreference in PropagationPolicy and ClusterPropagationPolicy. (@qianjun1993)
Support more convenient APIs to divide replicas by weight list
Users now able to declare cluster weight by ReplicaDivisionPreference in PropagationPolicy and ClusterPropagationPolicy, with the preference Weighted, the scheduler will divide replicas according to the WeightPreference. (@qianjun1993)
This feature is designed to replace the standalone ReplicaSchedulingPolicy API in the future.
Other Notable Changes
- karmada-agent: Introduced
--karmada-contextflag to indicate the cluster context in karmada kubeconfig file. (#415, @mrlihanbo) - karmada-agent and karmada-controller-manager: Introduced
--cluster-lease-durationand--cluster-lease-renew-interval-fractionflags to specify the lease expiration period and renew interval fraction. (#421, @pigletfly) - karmada-scheduler: Added a filter plugin to prevent the cluster from scheduling if the required API is not installed. (#470, @vincent-pli)
- karmada-controller-manager: Introduced
--skipped-propagating-apisflag to skip the resources from propagating. (#345, @pigletfly) - Installation: Now the
hack/deploy-karmada.shandhack/deploy-karmada-agent.shscripts support install Karmada components on bothKindclusters and standalone clusters. (#458, @lfbear) - In the case of resources already in member clusters, in order to avoid conflict karmada will refuse to propagate and adopt the resource by default. (#471, @mrlihanbo)
Contributors
Thank you to everyone who contributed to this release!
Users whose commits are in this release (alphabetically by user name)