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

The newly introduced API exposes HTTP and HTTPS routes that target multi-cluster services within the Karmada control plane. The specification of `MultiClusterIngress` is compatible with . Traffic routing is controlled by rules defined on the MultiClusterIngress resource, an MultiClusterIngress controller is responsible for fulfilling the ingress. The is one of the MultiClusterIngress controller implementations maintained by the community. The newly introduced provides constraints that limit total resource consumption per namespace `across all clusters`. It can limit the number of objects that can be created in a namespace by type, as well as the total amount of compute resources that may be consumed by resources in that namespace. The default number of reconciling workers has been enlarged and configurable. A larger number of workers means higher responsiveness but heavier CPU and network load. The number of concurrent workers could be configured by the flags introduced to `karmada-controller-manager` and `karmada-agent`. Flags introduced to `karmada-controller-manager`: `--concurrent-work-syncs` `--concurrent-namespace-syncs` `--concurrent-resource-template-syncs` `--concurrent-cluster-syncs` `--concurrent-clusterresourcebinding-syncs` `--concurrent-resourcebinding-syncs` Flags introduced to `karmada-agent`: `--concurrent-work-syncs` `--concurrent-cluster-syncs` Introduced `AggregateStatus` support for the `Resource Interpreter Webhook` framework, which enables customized resource status aggregating. Introduced `InterpreterOperationInterpretDependency` support for the `Resource Interpreter Webhook` framework, which enables propagating workload's dependencies automatically. Refer to for more details. `karmadactl` and `kubectl-karmada`: Fixed that init cannot update the `APIService`. `karmada-controller-manager`: Fixed ApplyPolicySucceed event type mistake (should be `Normal` but not `Warning`). `karmada-controller-manager` and `karmada-agent`: Fixed that resync slows down reconciliation. `karmada-controller-manager`/`karmada-agent`: Fixed continually updating cluster status due to unordered apiEnablements. `karmada-controller-manager`: Fixed that Replicas set by OverridePolicy will be reset by the ReviseReplica interpreterhook. `karmada-controller-manager`: Fixed that ResourceBinding couldn't be created in a corner case. `karmada-scheduler`: Fixed inaccuracy in requested resources in the case that pod limits are specified but requests are not. `karmada-scheduler`: Fixed spreadconstraints `karmadactl`: Introduced --tls-min-version flag to specify the minimum TLS version. `karmadactl`: Improved the get command to show more useful information. `karmada-controller-manager`/`karmada-agent`: Introduced --resync-period flag to specify reflector resync period (defaults to 0, meaning no resync). `karmada-controller-manager`: Introduced --metrics-bind-address flag to specify the customized address for metrics. `karmada-webhook`: Introduced --metrics-bind-address and --health-probe-bind-address flags. `karmada-controller-manager`: Fixed ApplyPolicySucceed event type mistake (should be Normal but not Warning). `OverridePolicy`/`ClusterOverridePolicy`: The `.spec.targetCluster` and `spec.overriders` have been deprecated in favor of `spec.overrideRules`. `karmada-aggregate-apiserver`: Deprecated `--master` and `--karmada-config` flags. Please use `--kubeconfig` instead.