karmada v0.3.0 release

What's New

Support override resources when propagating to member clusters

Users are now able to specify override policies to customize specific resource fields for different clusters. (#130, @RainbowMango, @mrlihanbo)

Support labelselector in cluster affinity

Users are now able to use ClusterAffinity.LabelSelector in PropagationPolicy API to restrict target clusters to when propagating resources. (#149, @mrlihanbo)

Support spread constraints

Users are now able to specify resource spread constraints in propagation policies:

• SpreadByFieldCluster: resource will be spread by clusters, it's useful for limiting number of clusters that a resource will be propagated to. (#162, #167, @kevin-wangzefeng , #168, @mrlihanbo)

More constraint options will be introduced in the later releases:

• SpreadByFieldRegion: resource will be spread by region.
• SpreadByFieldZone: resource will be spread by zone.
• SpreadByFieldProvider: resource will be spread by cloud providers.

Added webhook components to mutating and validating resources automatically
Introduced new components named karmada-webhook for implementating Mutating and Validationg webhooks. (#133, @RainbowMango)

Other Notable Changes

• E2E testing time consumption has been significantly reduced. (#119, @mrlihanbo)
• Provided generic client for operating both Kubernetes and Karmada APIs. (#126, @RainbowMango)
• The MemberCluster API is now Cluster. (#139, @kevin-wangzefeng)
• The API group propagationstrategy.karmada.io is now policy.karmada.io. (#142, @kevin-wangzefeng)
• Supported skip member cluster TLS verification. (#159, @mrlihanbo)
• Any unexpected modification of resource in member cluster will be amended automatically. (#127, @mrlihanbo)

karmada v0.2.0 release

Added scheduler framework and basic functionality(#108)

Signed-off-by: xuzhonghu <[email protected]>

karmada v0.1.0 release

update architecture and concepts

Signed-off-by: Kevin Wang <[email protected]>