Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration
APACHE-2.0 License
Bot releases are hidden (Show)
Published by kevin-wangzefeng over 3 years ago
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.
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.ResourceBinding
and ClusterResourceBinding
names now consist of resource kind
and resource name
.PropagationPolicy
and ClusterPropagationPolicy
names now restricted to no more than 63 characters.OverridePolicy
and ClusterOverridePolicy
changes will take effect immediately now.--cluster-status-update-frequency
when configuring karmada-agent
and karmada-controller-manager
, to specify cluster status update frequency.Thank you to everyone who contributed to this release!
Users whose commits are in this release (alphabetically by user name)
Published by kevin-wangzefeng over 3 years ago
New policy APIs have been added to support cluster level resources propagation and customization
Users are now able to use ClusterPropagationPolicy
to propagate both cluster-scoped and namespace-scoped resources. In addition, users are able to use ClusterOverridePolicy
to define the overall policy to realize differentiation propagation.
Support resource and policy detector
The detector watches both resources and policy (PropagationPolicy and ClusterPropagationPolicy) changes, all changes on resources or policies will take effect immediately.
Namespace Auto-provision feature get on board
Namespaces created on Karmada
will be synced to all member clusters automatically. Users don't need to propagate namespaces anymore.
Scheduler now able to reschedule resources when policy changes
Once the Placement
rule in the PropagationPolicy
changed, the scheduler will reschedule to meet the declaration.
Scheduler now support failure recovery
Once any of the clusters becomes failure, the scheduler now able to re-schedule the resources to available clusters.
This feature is controlled by flag --failover
and disabled by default.
PropagationWork
API is now Work
and located at the work.karmada.io
group.PropagationBinding
API is now ResourceBinding
and located at the work.karmada.io
group.karmada.io/driven-by
has been deprecated and replaced by propagationpolicy.karmada.io/namespace
, propagationpolicy.karmada.io/name
, and clusterpropagationpolicy.karmada.io/name
.karmada.io/created-by
has been deprecated and replaced by propagationpolicy.karmada.io/namespace
, propagationpolicy.karmada.io/name
, clusterpropagationpolicy.karmada.io/name
, resourcebinding.karmada.io/namespace
, resourcebinding.karmada.io/name
, clusterresourcebinding.karmada.io/name
, work.karmada.io/namespace
, work.karmada.io/name
.policy.karmada.io/applied-placement
for both ResourceBinding
and ClusterResourceBinding
resources, to indicate the placement rule.PropagationPolicy
and ClusterPropagationPolicy
objects.Thank you to everyone who contributed to this release!
Users whose commits are in this release (alphabetically by user name)
Published by kevin-wangzefeng over 3 years ago
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:
More constraint options will be introduced in the later releases:
Added webhook components to mutating and validating resources automatically
Introduced new components named karmada-webhook
for implementating Mutating and Validationg webhooks. (#133, @RainbowMango)
MemberCluster
API is now Cluster
. (#139, @kevin-wangzefeng)propagationstrategy.karmada.io
is now policy.karmada.io
. (#142, @kevin-wangzefeng)Published by kevin-wangzefeng almost 4 years ago
Published by kevin-wangzefeng almost 4 years ago