Project: Karmada (Orchestration & Management / Scheduling & Orchestration)
File: CHANGELOG-1.7.md

<!-- START doctoc generated TOC please keep comment here to allow auto update --> <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE --> Table of Contents generated with - - - - - - - - - - - - - - - - - - - - - <!-- END doctoc generated TOC please keep comment here to allow auto update --> Download v1.7.4 in the . `karmada-controller-manager`: Fixed incorrect annotation markup when policy preemption occurs. (, @XiShanYongYe-Chang) None. Download v1.7.3 in the . `karmada-controllr-manager`: concurrency of `binding-status controller` inherit from the concurrency of `binding` declared in global options. (, @lxtywypc) `karmada-search`: Add the logic of checking whether the resource API to be retrieved is installed in the cluster. (, @XiShanYongYe-Chang) `karmada-search`: support accept content type `as=Table` in the proxy global resource function. (, @jwcesign) The base image `alpine` now has been promoted from `alpine:3.18.5` to `alpine:3.19.1`. (, @Fish-pro) Download v1.7.2 in the . `karmada-controller-manager`: only update `aggregatedStatus` and `conditions` fields during `binding-status controller` updating status of binding. (, @jwcesign) `karmada-controller-manager`: Pruned job labels `batch.kubernetes.io/controller-uid` and `batch.kubernetes.io/job-name` which were introduced by Kubernetes 1.27. (, @liangyuanpeng) `karmada-search`: Fix lock race affects watch RestChan not close, causing client hanging when performing watch. (, @xigang) `karmada-operator`: Fixed can not load Karmada v1.7.0 crds issue. (, @liangyuanpeng) `release1.7`: The base image `alpine` now has been promoted from `alpine:3.18.3` to `alpine:3.18.5` (, @zhzhuang-zju) Karmada is now built with Go1.20.12. (, @RainbowMango) Download v1.7.1 in the . `karmada-aggregated-apiserver`: Fixed the issue that can not proxy `exec` request to a proxy issue. (, @jwcesign) `karmada-operator`: Fixed the issue that karmada-metrics-adapter was not removed after deleting a Karmada instance. (, @wawa0210) `karmada-controller-manager`: Fix panic when FederatedHPA's SelectPolicy is nil and FederatedHPA webhook is disabled. (, @watermeion) `karmada-webhook`: Fixed to validate spec.types of MultiClusterService API. (, @lonelyCZ) None. Download v1.7.0 in the . Introduced `CronFederatedHPA` API, which represents a collection of repeating schedules to scale the replica number of a specific workload. It is used for regular auto scaling scenarios, and it can scale any workloads that have a scale subresource or FederatedHPA. See for more details. (Feature contributors: @jwcesign, @chaunceyjiang, @RainbowMango) Introduced `MultiClusterService` API, which controls the exposure of services to multiple external clusters and also enables service discovery between clusters. See for more details. (Feature contributors: @XiShanYongYe-Chang, @chaunceyjiang, @yike21) The PropagationPolicy/ClusterPropagationPolicy is now able to preempt resources from another PropagationPolicy/ClusterPropagationPolicy as per priority by declaring the preemption behavior. Preemption will be disabled by default for backward

This feature is now controlled by feature gates `PropagationPolicyPreemption` with the alpha state (disabled by default). See for more details. (Feature contributors: @Poor12, @whitewindmills, @jwcesign, @RainbowMango) Legacy cluster resources can now be migrated to Karmada in batches by PropagationPolicy or ClusterPropagationPolicy. By specifying the `ConflictResolution` in the PropagationPolicy/ClusterPropagationPolicy, workloads can be migrated to Karmada smoothly without container termination or restarts. See for more details. (Feature contributors: @chaosi-zju, @RainbowMango) FederatedHPA is now able to scale replicas based on `custom metrics` in addition to CPU and memory. See for more details. (Feature contributor: @chaunceyjiang) Added print columns for `FederatedHPA` API including reference, minpods, maxpods, and replicas. (, @Poor12) Added `CronFederatedHPA` API based on . (, @RainbowMango) Introduced `Preemption` to both PropagationPolicy and ClusterPropagationPolicy to declare the behaviors of preemption. (, @RainbowMango) Introduced `ConflictResolution` to both PropagationPolicy and ClusterPropagationPolicy to declare how potential conflicts should be handled. (, @RainbowMango) Introduced a new field `Zones` to represent multiple zones of a member cluster. (, @RainbowMango) `karmada-controller-manager`: Removed `hpa` controller in favor of `FederatedHPA`. (, @jwcesign) The `Zone`(.spec.zone) was never used and now has been deprecated in favor of the newly introduced `Zones`. (, @RainbowMango) `karmadactl`: Deprecated `--cluster-zone` flag which will be removed in future releases and introduced `--cluster-zones` flag. (, @whitewindmills) `karmada-metrics-adapter`: Fixed the issue that when different clusters have the same pod name, the annotations of different metrics have the same value. (, @chaunceyjiang) `karmada-controller-manager`: Fixed panic when printing log in the case that lastSuccessfulTime of cronjob is nil. (, @chaunceyjiang) `karmada-controller-manager`: Fixed the issue that the `Applied` condition of ResourceBinding is always true. (, @chaunceyjiang) `karmada-controller-manager`: Fixed a boundary case where the `propagationpolicy.karmada.io/name` in the label of the resource template would not be removed after deleting PP. (, @chaunceyjiang) `karmada-controller-manager`: Fixed the issue that dependent resources are created and deleted repeatedly when the dependent resource has a status field. (, @chaunceyjiang) `karmada-controller-manager`: Avoid updating directly cached resource templates. (, @whitewindmills) `kamrada-controller-manager`: Fixed the issue that federated-HPA plain metric calculation is incorrect when usageRatio == 1.0, keep same with resource replicas. (, @zach593) `karmada-webhook`: When application failover is enabled, users are prevented from setting propagateDeps to `false`. (, @chaunceyjiang) `karmada-search`: Fixed a panic due to concurrent mutating objects in the informer cache. (, @ikaven1024) Fixed the inability to sync list issues in the case that the client disconnects from the member cluster. The fixes apply to the following components: karmada-controller-manager karmada-agent karmada-descheduler karmada-scheduler karmada-metrics-adapter karmada-search (, @WulixuanS) The base image `alpine` now has been promoted from `alpine:3.18.2` to

(, @Rajan-226) Security: Sets an upper bound for all components on the lifetime of idle keep-alive connections and time to read the headers of incoming requests. (, @zishen) `karmadactl`: The `--wait-component-ready-timeout` flag has been introduced in the `init` command to specify the component installation timeout. (, @helen-frank) `karmadactl`: Added `karmada-metrics-adapter` to addons. (, @chaunceyjiang) `karmadactl`: Introduced `top` command. (, @chaunceyjiang) `karmadactl join/register`, `karmada-agent`: Added labels on the namespace created by Karmada. (, @zhy76) `karmadactl`: Granted full permissions of Karmada resources to `admin` during deployment of Karmada with `init`. (, @zhy76) `karmada-controller-manager`: Supported aggregating the status of a pod's initContainer. (, @chaunceyjiang) `karmada-controller-manager`: Supported modification synchronization of custom resources as dependencies. (, @chaunceyjiang) `karmada-controller-manager`: Implemented proxy header of cluster APIs. (, @Poor12) `karmada-controller-manager`: The `--cluster-cache-sync-timeout` flag is now used to specify the sync timeout of the control plane cache in addition to the member cluster's cache. The default value has been increased to 2 minutes. (, @lxtywypc) `karmada-controller-manger`: Added Ingresses to the default dependencinterpreter. (, @chaunceyjiang) `karmada-controller-manager`: Introduced a LabelSelector field to DependentObjectReference. (, @chaunceyjiang) `karmada-controller-manager`: Added the pod replica interpreter by default. (, @whitewindmills) `karmada-controller-manager`: Added dependencies of ServiceImport to the default interpreter. (, @chaunceyjiang) `karmada-controller-manager`: Included the UID of the owner resource in labels and provided the details in annotations. If users are using related labels as label selectors, they should switch to using the UID as the label selector. (, @jwcesign) `karmada-scheduler`: Introduced new scheduling condition reasons: NoClusterFit, SchedulerError, Unschedulable, Success. (, @whitewindmills) `karmada-operator`: Supported disabling karmada cascading deletion. (, @calvin0327) `karmada-operator`: Allowed installing the `karmada-metrics-adapter` addon. (, @calvin0327) `karmada-webhook`: Allowed custom metrics configuration of FederatedHPA. (, @jwcesign) The base image `alpine` now has been promoted from `alpine:3.17.1` to `alpine:3.18.2`. (, @yanggangtony) Karmada is now built with Kubernetes v1.27.3 dependencies. (, @RainbowMango) Karmada(v1.7) is now built with Go 1.20.6. (, @parthn2) Fixed the issue that `karmada-search` no ETCD secret volume mount when using external ETCD. (, @my-git9) Granted full permissions of Karmada resources to `admin`. (, @Vacant2333) Now able to render `PodDisruptionBudget` for resources. (, @a7i) Karmada images now are signed with cosign. (, @liangyuanpeng) Removed specific labels from the following metrics of `karmada-controller-manager` to reduce the metrics count: resourcematchpolicydurationseconds: removed `apiVersion`/`kind`/`name`/`namespace`. resourceapplypolicydurationseconds: removed `apiVersion`/`kind`/`name`/`namespace`. policyapplyattempts_total: removed `namespace`/`name`. bindingsyncworkdurationseconds: removed `namespace`/`name`. worksyncworkloaddurationseconds: removed `namespace`/`name`. (, @jwcesign) Introduced the `TaintClusterSucceed` event to `Cluster` object and merged `TaintClusterByConditionFailed` and `RemoveTargetClusterFailed` to `TaintClusterFailed`. (, @Poor12) Introduced `cronfederatedhpaprocessdurationseconds` and `cronfederatedhparuleprocessduration_seconds` metrics for CronFederatedHPA. (, @whitewindmills) Introduced `federatedhpaprocessdurationseconds` and `federatedhpapullmetricsduration_seconds` for FederatedHPA, which will be emitted by `karmada-controller-manager`. (, @zhy76)