Skip to content

karmada v0.5.0 release
Compare
Choose a tag to compare
@kevin-wangzefeng kevin-wangzefeng released this 20 Apr 14:54
· 5864 commits to master since this release
v0.5.0
29c307c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's New

Support resource status aggregation from Karmada
Users are now able to query aggregated status of resources(propagated by Karmada) from Karmada API-server, no need to connect to each member cluster.
All resource's status in member clusters will be aggregated to its binding objects.
In addition, if the resource type is deployment, deployment status will be also reflected.

karmada-agent to support pull-based synchronization between control plan and member clusters
karmada-agent is introduced in this release to support cases the member clusters not directly reachable from the Karmada control plan.
The agent basically pulls all useful configurations from the Karmada control plane and applies to member clusters it serves.
The karmada-agent also completes cluster registration automatically.

ReplicaSchedulingPolicy API to customize replica scheduling constraints of Deployments
Users are now able to customize replica scheduling constraints of Deployments with ReplicaScheduling Policy API.
The replicas will be divided into different numbers for member clusters according to weight list indicated by the policy.

Other Notable Changes

  • The label karmada.io/override and karmada.io/cluster-override have been deprecated and replaced by policy.karmada.io/applied-overrides and policy.karmada.io/applied-cluster-overrides to indicate applied override rules.
  • The ResourceBinding and ClusterResourceBinding names now consist of resource kind and resource name.
  • Both PropagationPolicy and ClusterPropagationPolicy names now restricted to no more than 63 characters.
  • OverridePolicy and ClusterOverridePolicy changes will take effect immediately now.
  • Users are now able to use new flag --cluster-status-update-frequency when configuring karmada-agent and karmada-controller-manager, to specify cluster status update frequency.

Contributors

Thank you to everyone who contributed to this release!

Users whose commits are in this release (alphabetically by user name)

Assets 2
Loading