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

* * Download v1.2.0 in the . A new component `karmada-descheduler` was introduced, for rebalancing the scheduling decisions over time. One example use case is: it helps evict pending replicas (Pods) from resource-starved clusters so that `karmada-scheduler` can "reschedule" these replicas (Pods) to a cluster with sufficient resources. For more details please refer to By leveraging the newly added `spread-by-region` constraint, users are now able to deploy workloads across `regions`, e.g. people may want their workloads always running on different regions for HA purposes. We also introduced two plugins to `karmada-scheduler`, which add to accurate scheduling. `ClusterLocality` is a scoring plugin that favors clusters already assigned. `SpreadConstraint` is a filter plugin that filters clusters as per spread constraints. We are also in the progress of enhancing the multi-cluster failover mechanism. Part of the work has been included in this release. For example: A new flag(`--cluster-failure-threshold`) has been added to both `karmada-controller-manager` and `karmada-agent`, which specifies the cluster failure threshold (defaults to 30s). A cluster will be considered `not-ready` only when it stays unhealthy longer than supposed. A new flag(`--failover-eviction-timeout`) has been added to `karmada-controller-manager`, which specifies the grace period of eviction (defaults to 5 minutes). If a cluster stays `not-ready` longer than supposed, the controller taints the cluster. (Note: The taint is essentially the eviction order and the implementation is planned for the next release.) The `Aggregated API` was initially introduced in Release 1.0, which allows users to access clusters through Karmada by a single aggregated API endpoint. By leveraging this feature, we introduced a lot of interesting features to `karmadactl` and `kubectl-karmada`. The get sub-command now supports clusters both in push and pull mode. ```shell NAME CLUSTER READY UP-TO-DATE AVAILABLE AGE ADOPTION nginx member1 2/2 2 2 33h N nginx member2 1/1 1 1 4m38s Y podinfo member3 2/2 2 2 27h N ``` The newly added logs command prints the container logs in a specific cluster. ```shell /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/ /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf ... ``` We also added `watch` and `exec` commands to `karmadactl`, in addition to `get` and `logs`. They all use the aggregated API. The newly introduced `karmada-search` caches resources in clusters and allows users to search for resources without directly touching real clusters. ```shell { "apiVersion": "v1", "kind": "List", "metadata": {}, "items": [{ "apiVersion": "apps/v1", "kind": "Deployment", "metadata": { "annotations": { "cluster.karmada.io/name": "member1", }, } }, ] } ``` The `karmada-search` also supports syncing cached resources to backend stores like or . By leveraging the search engine, you can perform full-text searches with all desired features, by field, and by indice; rank results by score, sort results by field, and aggregate results. Introduced `InterpretStatus` for the `Resource Interpreter Webhook` framework, which enables customized resource status collection. Karmada can thereby learn how to collect status for your resources, especially custom resources. For example, a custom resource may have many status fields and only Karmada can collect only those you want. Refer to for more details. Benefiting from the Kubernetes native APIs, Karmada can easily integrate the Kubernetes ecosystem. The following components are verified by the Karmada community: `Kyverno`: policy engine. Refer to for more details. `Gatekeeper`: another policy engine. Refer to for more details. `fluxcd`: GitOps tooling for helm

Refer to for more details. karmadactl: Fixed the cluster joining failures in the case of legacy secrets. () karmadactl: Fixed the issue that you cannot use the '-v 6' log level. () karmadactl: Fixed the issue that the --namespace flag of init command did not work. () karmadactl: Allowed namespaces to be customized. () karmadactl: Fixed the init failure due to data path not clean. () karmadactl: Fixed the init failure to read the KUBECONFIG environment variable. () karmadactl: Fixed the init command failure to select the default release version. () karmadactl: Fixed the issue that the karmada-system namespace already exists when deploying karmada-agent. () karmadactl: Fixed the issue that the karmada-controller-manager args did not honor customized namespaces.` () karmadactl: Fixed a panic due to nil annotation when promoting resources to Karmada.` () karmadactl: Fixed the promote command failure to migrate cluster-scoped resources. () karmadactl: fixed the karmadactl taint failure while the karmada control plane config is not located in the default path. () helm-chart: Fixed the karmada-agent installation failure due to the lack of permission. ()) helm-chart: Fixed the issue that version constraints skip pre-releases. () karmada-controller-manager: Fixed the issue that ResourceBinding may hinder en-queue in the case of schedule failures. () karmada-controller-manager: Fixed the panic when the interpreter webhook returns nil patch. () karmada-controller-manager: Fixed the RB/CRB controller failure to aggregate status in the case of work condition update. () karmada-aggregate-apiserver: Fixed timeout issue when requesting cluster/proxy with options -w or logs -f from karmadactl get. () karmada-aggregate-apiserver: Fixed exec failed: error: unable to upgrade connection: you must specify at least 1 of stdin, stdout, stderr. () karmada-controller-manager: Introduced several flags to specify controller's concurrent capacities(--rate-limiter-base-delay, --rate-limiter-max-delay, --rate-limiter-qps, --rate-limiter-bucket-size). () karmada-controller-manager: The klog flags now have been grouped for better readability. () karmada-controller-manager: Fixed the FullyApplied condition of ResourceBinding/ClusterResourceBinding mislabeling issue in the case of non-scheduling. () karmada-controller-manager: Added default AggregateStatus webhook for DaemonSet and StatefulSet. () karmada-controller-manager: OverridePolicy with empty ResourceSelector will be considered to match all resources just like nil. () karmada-controller-manager: Introduced --failover-eviction-timeout to specify the grace period of eviction. Tants(cluster.karmada.io/not-ready or cluster.karmada.io/unreachable) will be set on unhealthy clusters after the period. () karmada-controller-manager/karmada-agent: Introduced --cluster-failure-threshold flag to specify cluster failure threshold. () karmada-scheduler: Workloads can now be rescheduled after the cluster is unregistered. () karmada-scheduler: The klog flags now have been grouped for better readability. () karmada-scheduler: Added a scoring plugin ClusterLocality to favor clusters already requested. () karmada-scheduler: Introduced filter plugin SpreadConstraint to filter clusters that do not meet the spread constraints. () karmada-scheduler: Supported spread constraints by region strategy. () karmada-webhook: Introduced --tls-cert-file-name and --tls-private-key-file-name flags to specify the server certificate and private key. () karmada-agent: The klog flags now have been grouped for better readability. () karmada-agent: Introduced several flags to specify controller's concurrent capacities(--rate-limiter-base-delay, --rate-limiter-max-delay, --rate-limiter-qps, --rate-limiter-bucket-size). () karmada-scheduler-estimator: The klog flags now have been grouped for better readability. () karmadactl: Introduced --context flag to specify the context name to use. () karmadactl: Introduced --kube-image-mirror-country and --kube-image-registry flags to init subcommand for Chinese mainland users. () karmadactl: Introduced deinit sub-command to uninstall Karmada. () Introduced Swagger docs for Karmada API. () The base image alpine has been promoted to v3.15.1. () karmada-controller-manager: The hpa controller is disabled by default now. () karmada-aggregated-apiserver: The deprecated flags --karmada-config and --master in v1.1 have been removed from the codebase. ()