karmada v0.9.0 release #784
kevin-wangzefeng
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What's New
Upgrading support
Users are now able to upgrade from the previous version smoothly. With the multiple version feature of CRD, objects with different schemas can be automatically converted between versions. Karmada uses the semantic versioning and will provide workarounds for inevitable breaking changes.
In this release, the
ResourceBiningandClusterResourceBindingpromote tov1alpha2and the previousv1alpha1version is still available for one more release. With the upgrading instruction, the previous version of Karmada can promote smoothly.(Feature contributor: @RainbowMango )
Introduced karmada-scheduler-estimator to facilitate end-to-end scheduling accuracy
Karmada scheduler aims to assign workload to clusters according to constraints and available resources of each member cluster. The
kube-schedulerworking on each cluster takes the responsibility to assign Pods to Nodes.Even though Karmada has the capacity to reschedule failure workload between member clusters, but the community still commits lots of effort to improve the accuracy of the end-to-end scheduling.
The
karmada-scheduler-estimatoris the effective assistant ofkarmada-scheduler, it provides prediction-based scheduling decisions that can significantly improve the scheduling efficiency and avoid the wave of rescheduling among clusters. Note that this feature is implemented as a pluggable add-on. For the instructions please refer to scheduler estimator guideline.(Feature contributor: @Garrybest )
Maintainability improvements
A bunch of significant maintainability improvements were added to this release, including:
Simplified Karmada installation with helm chart.
(Feature contributor: @algebra2k @jrkeen )
Provided metrics to observe scheduler status, the metrics API now served at
/metricsofkarmada-scheduler.With these metrics, users are now able to evaluate the scheduler's performance and identify the bottlenecks.
(Feature contributor: @qianjun1993 )
Provided events to Karmada API objects as supplemental information to debug problems.
(Feature contributor: @pigletfly )
Other Notable Changes
ResourceBinding/ClusterResourceBindingwon't be deleted after associatePropagationPolicy/ClusterPropagationPolicyis removed and is still available untilresource templateis removed.(@qianjun1993, keep ResourceBinding when removing PropagationPolicy #601)--leader-elect-resource-namespacewhich is used to specify the namespace of election object to components karmada-controller-manager/karmada-scheduler/karmada-agent`. (@XiShanYongYe-Chang introduce --leader-elect-resource-namespace flag #698)ReplicaSchedulingPolicyhas been deprecated and will be removed from the following release. The feature now has been integrated into ReplicaScheduling.kubectl-karmadacommands as the extensions forkubectl. (@XiShanYongYe-Chang introduce kubectl plugin #686)karmada-controller-managerintroduced aversioncommand to represent version information. (@RainbowMango Introduced version command to karmada-controller-manager #717 )karmada-scheduler/karmada-webhook/karmada-agent/karmada-scheduler-estimatorintroduced aversioncommand to represent version information. (@lonelyCZ add version command to components #719 )Submarinerto connect the network between member clusters. (@XiShanYongYe-Chang Add docs about working with submariner #737 )karmada-schedulerto monitor scheduler performance. (@qianjun1993 add metrics for scheduler #747)Contributors
Thank you to everyone who contributed to this release!
Users whose commits are in this release (alphabetically by user name)
This discussion was created from the release karmada v0.9.0 release.
Beta Was this translation helpful? Give feedback.
All reactions