Project: Karmada (Orchestration & Management / Scheduling & Orchestration)
File: CHANGELOG-1.4.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.4.5 in the . `karmada-search`: Fixed a panic due to concurrent mutating objects in the informer cache. (, @chaosi-zju) `karmada-controller-manager`: Avoid updating directly cached resource templates. (, @whitewindmills) None. Download v1.4.4 in the . `karmada-scheduler`: Fixed the issue that empty deployment can still be propagated to member clusters even when `--enableEmptyWorkloadPropagation` flag is false. (#3642, @chaunceyjiang) `karmada-controller-manager`: Fixed the panic issue in case of the grade number of resourceModel is less than the number of resources. (#3608, @sunbinnnnn) None. Download v1.4.3 in the . `karmada-search`: support pod subresource (attach, exec, port-forward) through global proxy. (#3100, @ikaven1024) `karmada-search`: Fixed the problem that ResourceVersion base64 encrypted repeatedly when starting multiple informers to watch resource. (#3388, @niuyueyang1996) `karmada-search`: Fixed paging list in karmada search proxy in large-scale member clusters issue. (#3450, @ikaven1024) `karmada-search`: Fixed contecnt-type header issue in HTTP response. (#3514, @callmeoldprince) `karmada-controller-manager`: Fixed the issue that RBAC resources whose name contains uppercase characters can not be propagated. (#3215, @whitewindmills) `karmada-controller-mamager`: Fixed Lua's built-in string function can not be used issue in ResourceInterpreterCustomization. (#3301, @chaunceyjiang) `karmada-controller-manager`: Fixed the control plane endpointslices cannot be deleted issue. (#3353, @wenchezhao) `karmadactl`: Fixed unable to view the options of `karmadactl addons enable/disable` issue. (#3306, @lonelyCZ) None. Download v1.4.2 in the . `karmada-controller-manager`: Fixed `LabelsOverrider` and `AnnotationsOverrider` failed to add new items issue in case of `label`/`annotation` is nil. (#2972, @chaunceyjiang) `karmada-controller-manager`: `labelsOverrider/annotationsOverrider` supports `composed-labels`, like testannotation/projectId: <label-value>. (#3047, @chaunceyjiang) `karmadactl`: Grant karmada-agent permission to access resourceinterpretercustomizations for `init` command. (#2986, @jwcesign) `karmada-agent`: Check if the resource exists before creating it. Sometimes the resource is created in advance, to give less privilege to Karmada. (#3002, @jwcesign) `karmada-search`: filter out not ready clusters. (#3016, @yanfeng1992) `karmada-search`: avoid proxy request block when member cluster down. (#3030, @ikaven1024) `karmada-webhook`: Fixed the issue that the InterpretDependency operation can't be registered. (#3074, @XiShanYongYe-Chang) None. Download v1.4.1 in the . `karmadactl`: Fixed `karmada-agent` installed by the `register` command can not delete works due to lack of permission issue. (#2904, @lonelyCZ) `karmadactl`: Fixed the default ValidatingWebhookConfiguration for `resourceinterpreterwebhook` not working issue. (#2924, @qingwave) `karmadactl`: Fixed the default ValidatingWebhookConfiguration for `resourceinterpretercustomizations` not working issue. (#2927, @chaunceyjiang) `karmadactl`: Fixed the error of resources whose name contains colons failing to be created when using `karmadactl apply`. (#2931, @Poor12) `karmada-controller-manager`/`karmada-agent`: Fixed misjudgment of deployment and statefuleset health status. (#2944, @Fish-pro) `karmada-controller-manager`/`karmada-agent`: Fixed failed to sync work status issue due to the informer being accidentally shut down. (#2937, @Poor12) `karmada-scheduler`: Fixed a corner case that re-schedule be skipped in case of the cluster becomes not fit. (#2955, @jwcesign) Karmada is now built with Golang 1.19.4. (#2913, @qingwave) Download v1.4.0 in the

The is designed for interpreting the structure of arbitrary resource types. It consists of `built-in` and `customized` interpreters, this release introduced another brand-new customized interpreter. With the newly introduced `declarative` , users can quickly customize resource interpreters for both Kubernetes resources and CRD resources by the rules declared in the `ResourceInterpreterCustomization` API specification. Compared with the interpreter customized by the webhook, it gets the rules from the declarative specifications instead of requiring an additional webhook component. The new command named `interpret` in the `karmadactl` could be used to test the rules before applying them to the system. Some examples are provided to help users better understand how this interpreter can be used. (Feature contributor: @jameszhangyukun @ikaven1024 @chaunceyjiang @XiShanYongYe-Chang @RainbowMango) Users are now able to declare the priority for both `PropagationPolicy` and `ClusterPropagationPolicy`, a policy will be applied for the matched resource templates if there are no other policies with higher priority at the point of the resource template be processed. The priority could be used by the system administrator to manage and control the policies. Refer to for more details. (Feature contributor: @Garrybest @jwcesign) This release enhanced observability significantly through metrics and events. The metrics can be queried by the endpoint(`/metrics`) of each component using an HTTP scrap, and they are served in Prometheus format. And the events are reported to the relevant resource objects respectively. Refer to and for more details. (Feature contributor: @Poor12) Introduce priority to PropagationPolicy. (, @RainbowMango) Introduced `LabelsOverrider` and `AnnotationsOverrider` for overriding labels and annotations.(, @chaunceyjiang) evolute PropagateDeps FeatureGate to Beta and enable it by default. (, @XiShanYongYe-Chang) evolute Failover/GracefulEviction FeatureGate to Beta and enable it by default. (, @jwcesign) evolute CustomizedClusterResourceModeling FeatureGate to Beta and enable it by default. (, @Poor12) `karmada-search`: fix concurrent map writes panic while list objects via proxy. (, @ikaven1024) `karmada-search`: Fixed returned ResourceVersion by proxy not stable issue. (, @cmicat) `karmada-controller-manager`/`karmada-agent`: Fixed pod information can not be collected issue when building resource summary. (, @Poor12) `karmada-controller-manager`: use cluster secret ref namespace in unified-auth-controller when generate ClusterRoleBinding. (, @XiShanYongYe-Chang) `karmada-controller-manager`: fix the error of resources whose name contains colons failing to be created. (, @XiShanYongYe-Chang) `karmada-controller-manager`: Fixed the panic when cluster ImpersonatorSecretRef is nil.(, @stingshen) `karmada-controller-manager`: Fix serviceaccount continual regeneration by service account controller.(, @Poor12) `karmada-controller-manager`: Disable the preemption matching of pp/cpp priority. (, @XiShanYongYe-Chang) `karmada-controller-manager`: Fix clusterOverridePolicy and overridePolicy with nil resource selector could not work. (, @wuyingjun-lucky) `karmada-controlle-managerr`: ignore resource that do not match with policy before apply policy. (, @XiShanYongYe-Chang) `karmada-agent`: Fixed `ServiceExport` controller can not report `endpointSlices` issue(due to miss `create` permission). (, @lonelyCZ) `karmadactl`: Fixed `init` can not honor IPV6 address issue when generating kubeconfig file. (, @duanmengkk) `karmadactl`: Fixed `--karmada-data` directory not initialization issue in `init` command. (, @jwcesign) `karmadactl`: Fixed `init` commands print incorrect register command issue. (, @Songjoy) `karmadactl`: Fix namespace already exists. (, @cleverhu) `karmada-webhook`: Fixed failed to set resource selector default namespace if the relevant OverridePolicy and PropagationPolicy with namespace unset issue. (, @carlory) `Security`: Add limitReader to `io.ReadAll` which could limit the memory request and avoid DoS attacks. (, @Poor12) `karmadactl`: Improve karmada init help

(, @my-git9) `karmadactl`: karmadactl prohibit input extra arguments for `init` command. (, @helen-frank) `karmadactl`/`chart`: The `init` no longer creates redundant ServiceAccounts for components except `karmada-agent`. (, @carlory) `karmadactl`: Fixed options of `deinit` can not be shown issue. (, @helen-frank) `karmadactl/chart`: if karmada is installed by using karmadactl or helm chart with default configuration, the image version of karmada-kube-controller-manager/karmada-apiserver will be kube-controller-manager:v1.25.2/kube-apiserver:v1.25.2. (, @jwcesign) `karmadactl`: Introduced `--karmada-apiserver-advertise-address` flag to specify Karmada APIserver's address to the `init` sub-command. (, @wuyingjun-lucky) `karmadactl`: introduce --enable-cert-rotation option to register command.(, @lonelyCZ) `karmadactl`: uncordon add dryrun (, @helen-frank) `karmadactl`: karmadactl get add validate cluster exist (, @helen-frank) `karmadactl`: add liveness probe into the kube-controller-manager component (, @carlory) `karmadactl`: `init` add `--image-registry` flags (, @helen-frank) `karmadactl`: add interpreter command for resource interpret customizations. (, @ikaven1024) `karmadactl`: add execute mod for interpret command. (, @ikaven1024) `karmada-search`: objects returned by proxy will have `resource.karmada.io/cached-from-cluster` annotation to indicate which member cluster from. (, @ikaven1024) `karmada-search`: users can get the real resource request metrics while using the proxy. (, @ikaven1024) `karmada-search`: users now can use `--disable-search` and `--disable-proxy` options to disable search and proxy feature (default both are enabled).(, @ikaven1024) `karmada-controller-manager`: add implicit priority for PropagationPolicy. (, @Garrybest) `karmada-controller-manager`: Introduced resource label `namespace.karmada.io/skip-auto-propagation: "true"` which can label the namespaces that should be skipped from auto propagation.(, @jwcesign) `karmada-controller-manager`: allow users to update the `.spec.resourceSelectors` filed of `PropagationPolicy/ClusterPropagationPolicy`. (, @XiShanYongYe-Chang) karmada-controller-manager`: Introduce priority to PropagationPolicy. (, @jwcesign) `karmada-scheduler-estimator`: leverage scheduler cache to estimate replicas.(, @Garrybest) `karmada-controller-manager`: do not propagate finalizers to member cluster (, @stingshen) `karmada-scheduler`/`karmada-scheduler-descheduler`: Introduced `--scheduler-estimator-service-prefix` flag for discovery estimators.(, @carlory) `karmada-scheduler`: add scheduling diagnosis.(, @Garrybest) `karmada-agent`: introduce auto certificate rotation function.(, @lonelyCZ) `karmada-webhook`: Prevent modifying and creating `ResourceInterpreterCustomization` using the same interpretation rules. (, @chaunceyjiang) validate cluster fields: provider, region and zone. (, @carlory) Download images from docker hub by default. (, @jwcesign) Karmada is now built with Golang 1.19.3. (, @RainbowMango) `Helm Chart`: add descheduler name suffix of chart deployment manifest (, @calvin0327) `HelmChart`: Fixed liveness probe misconfiguration which caused kube-controller-manager to always `CrashLoopBackup`. (, @calvin0327 ) `chart`: Fix use custom certs lead to post-install-job failed and kube-controller-manager crash by missing /etc/karmada/pki/server-ca.key.(, @631068264) `Instrumentation`: Introduced the `GetDependenciesSucceed` and `GetDependenciesFailed` to the resource template. Introduced the `SyncScheduleResultToDependenciesSucceed` and `SyncScheduleResultToDependenciesFailed` to `resourceBinding` object. (, @Poor12 ) `Instrumentation`: Introduce `EvictWorkloadFromClusterSucceed`, `EvictWorkloadFromClusterFailed` to the `binding` object and its reference. Refactor the event name of `TaintManagerEviction`. (, @Poor12) `Instrumentation`: Introduced the `resourcefindmatchedpolicydurationseconds`, `resourceapplypolicydurationseconds`, `policyapplyattemptstotal`, `bindingsyncworkdurationseconds`, `worksyncworkloaddurationseconds` metrics. (, @Poor12 ) `Instrumentation`: Introduced the `CreateExecutionSpaceSucceed` and `RemoveExecutionSpaceSucceed` events to `Cluster` object. (, @Poor12) `Instrumentation`: Introduced the `ApplyOverridePolicySucceed` and `ApplyOverridePolicyFailed` events to workload. (, @Poor12) `Instrumentation`: Introduced the `ReflectStatusToWorkSucceed`, `ReflectStatusToWorkFailed`, `InterpretHealthSucceed` and `InterpretHealthFailed` events to `work` object. (, @Poor12) `Instrumentation`: Introduced the `SyncImpersonationConfigSucceed` and `SyncImpersonationConfigFailed` to the `cluster` object.(, @Poor12) `Instrumentation`: Apply `AggregateStatusFailed`, `AggregateStatusSucceed`, `SyncWorkSucceed`, and `SyncWorkFailed` to the `federatedResourceQuota` object. (, @Poor12) `Instrumentation`: introduce `SyncDerivedServiceSucceed` and `SyncDerivedServiceFailed` to the `serviceImport` object. (, @Poor12) `Instrumentation`: Introduced the `clusterreadyinfo`, `clusternodenumber`, `clusterreadynodenumber`, `clustermemoryallocatablebytes`, `clustercpuallocatablenumber`, `clusterpodallocatablenumber`, `clustermemoryallocatedbytes`, `clustercpuallocatednumber`, `clusterpodallocatednumber`, `clustersyncstatusduration` to record the cluster status in `karmada-controller-manager` and `karmada-agent`. (@Poor12 `Instrumentation`: introduced the `frameworkextensionpointdurationseconds` and `pluginexecutionduration_seconds` metrics for `karmada-scheduler`.(, @Poor12)