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

* * Download v1.3.0 in the . We introduced a new controller named `taint manager` which aims to evict workloads from faulty clusters after a grace period. Then the scheduler would select new best-fit clusters for the workloads. In addition, if the feature `GracefulEviction` is enabled, the eviction will be very smooth, that is, the removal of evicted workloads will be delayed until the workloads are available on new clusters or reach the maximum grace period. For more details please refer to . (Feature contributor: @Garrybest, @XiShanYongYe-Chang) We introduced a new proxy feature to `karmada-search` that allows users to access resources in multiple clusters in a way just like accessing resources in a single cluster. No matter whether the resources are managed by Karmada, by leveraging the proxy, users can manipulate the resources from the Karmada control plane. For more details please refer to . (Feature contributor: @ikaven1024, @XiShanYongYe-Chang) To provide a more accurate scheduling basis for the scheduler, we introduced a way to model the cluster's available resources. The cluster status controller will model the resources as per the customized resource models, which is more accurate than the general resource summary. For more details please refer to . (Feature contributor: @halfrost, @Poor12) Now for clusters in `Pull` mode, we provide a way for them to register with the Karmada control plane. By leveraging the commands `token` and `register` in `kubectl`, the registration process including deploying the `karmada-agent` can be completed very easily. For more details please refer to . (Feature contributor: @lonelyCZ ) We improved the system scalability, such as: Enable pprof() Introduce `cachedRESTMapper`() Adopt the transform function to reduce memory usage() With these improvements, Karmada can easily manage hundreds of huge clusters. The detailed test report will be released soon. The `Cluster` API is added optional field `ID` to uniquely identify the cluster. (@RainbowMango, ) The `Cluster` API is added optional field `ProxyHeader` to specify the HTTP header required by the proxy server. (@mrlihanbo, ) The `Cluster` API is added optional field named `ResourceModels` to specify resource modeling. (@halfrost, ) The `Work` and `ResourceBinding`/`ClusterResourceBinding` APIs are added field `health` to represent the state of workload. (@XiShanYongYe-Chang, ) `karmadactl`: Fixed issue that Kubernetes v1.24 cannot be joined. (@zgfh, ) `karmadactl`: Fixed a panic issue when retrieving resources from an unknown cluster(`karmadactl get xxx --cluster=not-exist`). (@my-git9, ) `karmadactl`: Fixed failed promoting if a resource with another kind using the same name has been promoted before. (@wuyingjun-lucky, ) `karmada-search`: Fixed panic when the resource annotation is nil. (@XiShanYongYe-Chang, ) `karmada-search`: Fixed panic `comparing uncomparable type cache.ResourceEventHandlerFuncs`. (@liys87x, ) `karmada-search`: Fixed failed query on a single namespace (@luoMonkeyKing, ) `karmada-controller-manager`: Fixed that `Job` status might be incorrectly marked as `Completed`. (@Garrybest, ) `karmada-controller-manager`: Fixed returning err when the interpreter webhook returns nil patch and nil patchType. (@CharlesQQ, ) `karmada-controller-manager`: Fixed that Argo CD cannot assess Deployment health status. (@xuqianjins, ) `karmada-controller-manager`: Fixed that Argo CD cannot assess StatefulSet/DaemonSet health status. (@RainbowMango, ) `karmada-controller-manager`/`karmada-agent`: Fixed an resource status can not be collected issue in case of Resource Interpreter returns an error. (@XiShanYongYe-Chang, ) `karmada-sechduler`: Fixed a panic issue when `replicaDivisionPreference` is `Weighted` and `WeightPreference` is nil. (@XiShanYongYe-Chang, ) `karmadactl`: Added `--force` flag to `deinit` to skip confirmation. (@zgfh, ) `karmadactl`: The flag `-c` of sub-command `promote` now has been changed to uppercase `-C`. (@Fish-pro, ) ``karmadactl`: Introduced `--cluster-zone` and `--cluster-region` flags to `join` command to specify the zone and region of joining cluster. (@chaunceyjiang, ) `karmadactl`: Introduced `--namespace` flag to `exec` command to specify the workload

(@carlory, ) `karmadactl`: Allowed reading namespaces from the context field of karmada config for `get` command. (@carlory, ) `karmadactl`: Introduced `apply` subcommand to apply a configuration to a resource by file name or stdin. (@carlory, ) `karmadactl`: Introduced `--namespace` flag to `describe` command to specify the namespace the workload belongs to. (@TheStylite, ) `karmadactl`: Introduced `--cluster` flag for `apply` command to allow users to select one or many member clusters to propagate resources. (@carlory, ) `karmadactl`: Introduced options subcmd to list global command-line options. (@lonelyCZ, ) `karmadactl`: Introduced the` token` command to manage bootstrap tokens. (@lonelyCZ, ) `karmadactl`: Introduced the` register` command for joining PULL mode cluster. (@lonelyCZ, ) `karmada-scheduler`: Introduced `--enable-empty-workload-propagation` flag to enable propagating empty workloads. (@CharlesQQ, ) `karmada-scheduler`: Allowed extended plugins in an out-of-tree mode. (@kerthcet, ) `karmada-scheduler`: Introduced `--disable-scheduler-estimator-in-pull-mode` flag to disable scheduler-estimator for clusters in pull mode. (@prodanlabs, ) `karmada-scheduler`: Introduced `--plugins` flag to enable or disable scheduler plugins. (@chaunceyjiang, ) `karmada-scheduler`: Now the scheduler starts to re-schedule in case of cluster state changes. (@chaunceyjiang, ) `karmada-search`: The search API supports searching for resources according to labels. (@XiShanYongYe-Chang, ) `karmada-search`: The annotation `cluster.karmada.io/name` which is used to represent the source of cache now has been changed to `resource.karmada.io/cached-from-cluster`. (@calvin0327, ) `karmada-search`: Fixed panic issue when dumping error info. (@AllenZMC, ) `karmada-controller-manager/karmada-agent`: Cluster state controller now able to collect partial API list in the case of discovery failure. (@duanmengkk, ) `karmada-controller-manager/karmada-agent`: Introduced `--cluster-success-threshold` flag to specify cluster success threshold. Default to 30s. (@dddddai, ) `karmada-controller-manager/karmada-agent`: Added CronJob support to the default resource interpreter framework. (@chaunceyjiang, ) `karmada-controller-manager`/`karmada-agent`: Introduced `--leader-elect-lease-duration`, `--leader-elect-renew-deadline` and `--leader-elect-retry-period` flags to specify leader election behaviors. (@CharlesQQ, ) `karmada-controller-manager`/`karmada-agent` : Fixed panic issue when dumping error infos. (@AllenZMC, ) `karmada-controller-manager`/`karmada-agent`: Supported interpreting health state by levering `Resource Interpreter Framework`. (@zhuwint, ) `karmada-controller-manager`/`karmada-agent`: Introduced `--enable-cluster-resource-modeling` flag to enable or disable cluster modeling feature. (@RainbowMango, ) `karmada-controller-manager`/`karmada-agent`: Now able to retain `.spec.claimRef` field of `PersistentVolume`. (@Garrybest, ) `karmada-controller-manager`: `interpreter framework` starts to support Pod state aggregation. (@xyz2277, ) `karmada-controller-manager`: `interpreter framework` starts to support PVC state aggregation. (@chaunceyjiang, ) `karmada-controller-manager`: Stopped reporting and refreshing `lease` for clusters in `Push` mode. (@dddddai, ) `karmada-controller-manager`: `interpreter framework` starts to support Pod `Failded` and `Succeeded` aggregation. (@chaunceyjiang, ) `karmada-controller-manager`: `namespace` controller starts to apply `ClusterOverridePolicy` during propagation namespaces. (@zirain, ) `karmada-controller-manager`: Propagation dependencies support propagating ServiceAccounts. (@chaunceyjiang, ) `karmada-agent`: Introduced `--metrics-bind-address` flag to specify the address for serving Prometheus metrics. (@1953, ) `karmada-agent`: Introduced `--report-secrets` flag to allow secrets to be reported to the Karmada control plane during registering. (@CharlesQQ, ) `karmada-agent`: Introduced `--cluster-provider` and `--cluster-region` flags to specify cluster-provider and cluster-region during registering. (@CharlesQQ, ) `karmada-webhook`: Added default tolerations, defaultNotReadyTolerationSeconds, and defaultUnreachableTolerationSeconds, for (Cluster)PropagationPolicy. (@Garrybest, ) `karmada-webhook`: The '.spec.ttlSecondsAfterFinished' field of the Job resource will be removed before propagating to member clusters. (@chaunceyjiang, ) `karmada-agent`/`karmadactl`: Now an error will be reported when registering the same cluster to Karmada. (@yy158775, ) `Helm chart`: Updated default `kube-apiserver` from v1.21 to v1.22. (@AllenZMC, ) `Helm Chart`: Added missing `APIService` configuration for `karmada-aggregated-apiserver`. (@zhixian82, ) `Helm Chart`: Fixed the webhook service mismatch issue in the case of customized release name. (@calvin0327, ) `Helm Chart`: Introduced `--cluster-api-endpoint` for `karmada-agent`. (@my-git9, ) `Helm Chart`: Fixed misconfigured `MutatingWebhookConfiguration`. (@zhixian82, ) Karmada is now built with Golang 1.18.3. (@RainbowMango, ) All Kubernetes dependencies are now updated to v1.24.2. (@RainbowMango, ) `karmadactl`: Removed `--dry-run` flag from `describe`, `exec` and `log` commands. (@carlory, ) `karmadactl`: Removed the `--cluster-namespace` flag for `get` command. (@carlory, ) `karmadactl`: Removed the `--cluster-namespace` flag for `promote` command. (@carlory, )