karmada v1.0.0 release #1203
Replies: 2 comments 2 replies
-
|
Great improvement !! |
Beta Was this translation helpful? Give feedback.
-
|
Done. |
Beta Was this translation helpful? Give feedback.
-
|
Regarding the "Verified Integration with Ecosystem", any plan to involve KubeEdge? |
Beta Was this translation helpful? Give feedback.
-
|
Good question! We are glad to see people share any integration status with us, not only KubeEdge. |
Beta Was this translation helpful? Give feedback.
-
What's New
Aggregated Kubernetes API Endpoint
The newly introduced
karmada-aggregated-apiservercomponent aggregates all registered clusters and allows users to access member clusters through Karmada by the proxy endpoint, e.g.Please refer to user guide for more details.
(Feature contributor: @kevin-wangzefeng @GitHubxsy @XiShanYongYe-Chang @mrlihanbo @jrkeen @prodanlabs @carlory @RainbowMango)
Promoting Workloads from Legacy Clusters to Karmada
Legacy workloads running in Kubernetes now can be promoted to Karmada smoothly without container restart.
In favor of
promotecommands added to Karmada CLI, any kind of Kubernetes resources can be promoted to Karmada easily, e.g.Please refer to promote legacy workload for more details.
(Feature contributor: @iawia002 @lonelyCZ @dddddai)
Verified Integration with Ecosystem
Benefiting from the Kubernetes native API support, Karmada can easily integrate the single cluster ecosystem for multi-cluster, multi-cloud purpose. The following components have been verified by the Karmada community:
argo-cd: refer to working with argo-cdFlux: refer to propagating helm charts with fluxIstio: refer to working with IstioFilebeat: refer to working with FilebeatSubmariner: refer to working with SubmarinerVelero: refer to working with VeleroPrometheus: refer to working with Prometheus(Feature contributor: @lfbear @learner0810 @zirain @Rains6 @gy95 @XiShanYongYe-Chang )
OverridePolicy Improvements
By leverage of the new-introduced
RuleWithClusterfields toOverridePolicyandClusterOverridePolicy, users are now able to define override policies with a single policy for specified workloads.(Feature contributor: @iawia002 @lfbear @RainbowMango @lonelyCZ @jameszhangyukun )
Karmada Installation Improvements
Introduced
initcommand toKarmada CLI. Users are now able to install Karmada by a single command.Please refer to Installing Karmada for more details.
(Feature contributor: @prodanlabs @lonelyCZ @jrkeen )
Configuring Karmada Controllers
Now all controllers provided by Karmada work as plug-ins. Users are now able to turn off any of them from the default enabled list.
See
--controllersflag ofkarmada-controller-managerandkarmada-agentfor more details.(Feature contributor: @snowplayfire @iawia002 @jameszhangyukun )
Resource Interpreter Webhook Enhancement
Introduced
ReviseReplicasupport for theResource Interpreter Webhookframework, which enables scheduling all customized workloads just like Kubernetes native ones.Refer to Resource Interpreter Webhook Proposal for more design details.
(Feature contributor: @iawia002)
Other Notable Changes
Bug Fixes
karmada-controller-manager: Fixed the issue that the annotation of resource template cannot be updated. (@mrlihanbo support update object annotations #1012)karmada-controller-manager: Fixed the issue of generating binding reference key. (@JarHMJ fix: fix GenerateBindingReferenceKey bug #1003)karmada-controller-manager: Fixed the inefficiency of en-queue failed task issue. (@Garrybest Work status reflection is too slow because of async worker enqueue rate limit #1068)Features & Enhancements
Karmada CLI: Introduced--cluster-providerflag tojoincommand to specify provider of joining cluster. (@2hangchen Specify the provider manually. #1025)Karmada CLI: Introducedtaintcommand to set taints for clusters. (@lonelyCZ Implement karmadactl taint to add taints into a cluster #889)Karmada CLI: TheAppliedcondition ofWorkandScheduled/FullyAppliedofResourceBindingare available forkubectl get. (@lonelyCZ Add more printcolumn for rb, crb and work when executing kubectl get #1110)karmada-controller-manager: The cluster discovery feature now supportsv1beta1ofcluster-api. (@iawia002 Support for the cluster-api v1beta1 version #1029)karmada-controller-manager: TheJob'sstartTimeandcompletionTimenow available at resource template. (@Garrybest add startTime and completionTime in job status #1034)karmada-controller-manager: introduced--controllersflag to enable or disable controllers. (@snowplayfire introduce--controllersflag to contrl controllers for karmada-controller-manager #1083)karmada-controller-manager: Support retainownerReferencefrom observed objects. (@snowplayfire retain ownerReferences when update member cluster object #1116)karmada-controller-managerandkarmada-agent: Introducedcluster-cache-sync-timeoutflag to specify the time waiting for cache sync. (@snowplayfire set default for clusterCacheSync timeout and make it configurable #1112)Instrumentation (Metrics and Events)
karmada-scheduler-estimator: Introduced/metricsendpoint to emit metrics. (@Garrybest add metrics for scheduler estimator #1030)ApplyPolicyandScheduleBindingevents for resource template. (@mrlihanbo add events to resource template #1070)Deprecation
ReplicaSchedulingPolicyAPI deprecated at v0.9.0 now has been removed in favor ofReplicaSchedulingofPropagationPolicy. (@iawia002 Remove deprecated ReplicaSchedulingPolicy API #1161)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 v1.0.0 release.
Beta Was this translation helpful? Give feedback.
All reactions