RATATOSKRATATOSK
ログイン

Karmada

v1.18.3Orchestration & Management
2026年8月31日

ACTION 4CHECK 1PLAN 3OTHER 108

機能拡張に加え、正確性の改善と依存関係の更新を含む、変更範囲の広いリリースです。API、スケジューリング、インタープリター、可観測性に関わる拡張がある一方、非推奨化やデフォルト値の変更、設定経路の削除もあります。セキュリティ対応の依存関係更新も含まれるため、アップグレード前に互換性と設定変更の確認が必要です。

要対応 (4)

  • securitymediumgithub.com/vektra/mockery の更新

    セキュリティ上の懸念に対応するため、github.com/vektra/mockery を v3.5.5 に更新しました。対象となる勧告は GO-2025-3900 です。

  • securityalpine ベースイメージの更新

    ベースイメージ alpine を alpine:3.23.4 から alpine:3.24.1 に更新し、セキュリティ上の懸念に対応しました。

    karmada#7628karmada#7652

  • securityalpine ベースイメージの更新

    ベースイメージ alpine を alpine:3.23.3 から alpine:3.23.4 に更新し、セキュリティ上の懸念に対応しました。

    karmada#7410

  • breakingメンバークラスタークライアントのデフォルトタイムアウト

    メンバークラスターが応答しない際にコントローラーが停止した状態になることを避けるため、メンバークラスタークライアントに 32 秒のデフォルトタイムアウトを追加しました。

影響確認 (1)

  • breakingkarmada-operator の外部 etcd フィールド削除

    CAData、CertData、KeyData のいずれかを使用している場合に適用されます。

    karmada-operator から、外部 etcd 用として非推奨だったフィールド CAData、CertData、KeyData を削除しました。

事前準備 (3)

  • breaking外部 etcd フィールドの削除

    CAData、CertData、KeyData のいずれかを使用している場合に適用されます。

    外部 etcd 用として非推奨だったフィールド CAData、CertData、KeyData を削除しました。

  • deprecated--etcd-init-image の非推奨化削除時期は未定

    --etcd-init-image を使用している場合に適用されます。

    init コマンドのフラグ --etcd-init-image は使用されなくなったため非推奨になり、今後のリリースで削除されます。

  • breakingメトリクスラベルの member_cluster への変更削除時期は未定

    メトリクスで cluster または cluster_name を使用している場合に適用されます。

    Karmada のメンバークラスターを示していた Prometheus メトリクスラベル cluster と cluster_name は非推奨になり、1.18 リリースで削除されます。今後は member_cluster を使用します。

その他の記録済み変更 108 件すべてfixes 42 · additions 37 · value changes 19 · constraints 8 · defaults 2

fixes (42)

  • - karmada-controller-manager: Fixed an issue where the taint-manager eviction queue would enqueue bindings with indefinite taint tolerations. ([#7775](https://github.com/karmada-io/karmada/pull/7775), @karmada-bot)
  • - karmada-controller-manager: Fixed an issue where Cluster.status.remedyActions could remain stale after an associated Remedy resource was removed. ([#7790](https://github.com/karmada-io/karmada/pull/7790), @karmada-bot)
  • - helm chart: Fixed TLS certificate SAN mismatch when deploying to a custom namespace by adding systemNamespace SANs to certs.auto.hosts. ([#7686](https://github.com/karmada-io/karmada/pull/7686), @karmada-bot)
  • #### Bug Fixes - karmada-search: Fixed the issue that watch connect cannot reflect resources from recovered clusters immediately. ([#7522](https://github.com/karmada-io/karmada/pull/7522), @Ady0333)
  • - karmada-scheduler: Fixed the issue when cluster resources are insufficient, multiple template resources can still be scheduled. ([#7580](https://github.com/karmada-io/karmada/pull/7580), @jabellard)
  • - karmada-controller-manager: Fixed the issue that a transient ClusterClientSetFunc failure (e.g. missing SecretRef during credential rotation) would immediately set the cluster Ready=False without respecting ClusterFailureThreshold, potentially triggering unnecessary workload failover. ([#7578](https://github.com/karmada-io/karmada/pull/7578), @driegel1)
  • - karmada-operator: Fixed init reconciliation failure by replacing non-idempotent secret creation with an idempotent approach. ([#7405](https://github.com/karmada-io/karmada/pull/7405), @anr)
  • - karmada-scheduler: Fixed an issue where the schedule success event was missing cluster information when scheduling with ClusterAffinities. ([#7419](https://github.com/karmada-io/karmada/pull/7419), @cotishq)
  • - karmada-scheduler: Fixed incorrect error type propagation that caused bindings with insufficient cluster replicas to be misrouted to backoffQ instead of unschedulableBindings. ([#7354](https://github.com/karmada-io/karmada/pull/7354), @SujoyDutta)
  • - Fixed the issue that Job completions were assigned to the wrong replicas for each cluster. ([#7401](https://github.com/karmada-io/karmada/pull/7401), @Ady0333)
  • - karmada-agent: Fixed the issue where certificate rotation CSRs were never auto-approved due to a SignerName mismatch between cert_rotation_controller and agent_csr_approving. ([#7310](https://github.com/karmada-io/karmada/pull/7310), @Denyme24)
  • - karmada-chart: Fixed unrendered {{ ca_crt }} during upgrades. ([#7330](https://github.com/karmada-io/karmada/pull/7330), @AbhinavPInamdar)
  • - karmada-controller-manager: Fixed a race condition where graceful eviction tasks could be silently dropped when multiple controllers concurrently modify the same ResourceBinding or ClusterResourceBinding, preventing workloads from being evacuated from tainted or failing clusters. ([#7307](https://github.com/karmada-io/karmada/pull/7307), @Ady0333)
  • - karmada-controller-manager: Fixed the issue where the job status aggregator could enter an error loop due to a race condition when setting the initial startTime. ([#7158](https://github.com/karmada-io/karmada/pull/7158), @rohan-019)
  • - karmada-controller-manager: Fixed CronFederatedHPA scale-up from zero failure when the replicas field is missing. ([#7212](https://github.com/karmada-io/karmada/pull/7212), @zhengjr9)
  • - karmada-controller-manager: Fixed an issue where a per-task GracePeriodSeconds value could leak to subsequent graceful eviction tasks, causing premature or delayed evictions. ([#7187](https://github.com/karmada-io/karmada/pull/7187), @Ady0333)
  • - karmada-controller-manager: Fixed an issue where dependency updates could overwrite other controller annotations during retry conflicts. ([#7216](https://github.com/karmada-io/karmada/pull/7216), @Ady0333)
  • - karmada-scheduler: Fixed a scheduler panic caused by a divide-by-zero error when calculating spread constraints with no valid clusters. ([#7234](https://github.com/karmada-io/karmada/pull/7234), @XiShanYongYe-Chang)
  • - karmada-scheduler: Fixed the bug in the backoff queue where the sorting function was incorrect, potentially causing high-priority items with long backoffs to block lower-priority items. ([#7231](https://github.com/karmada-io/karmada/pull/7231), @zhzhuang-zju)
  • - karmada-scheduler-estimator: Fixed the issue where the resource quota plugin failed to list resource quotas due to a missing namespace in the gRPC request. ([#7238](https://github.com/karmada-io/karmada/pull/7238), @zhzhuang-zju)
  • #### Bug Fixes - karmada-controller-manager: Fixed an issue where policy deletion could be blocked if a resource selector targeted a non-existent resource. ([#7083](https://github.com/karmada-io/karmada/pull/7083), @FAUST-BENCHOU)
  • - karmada-scheduler: Fixed bug preventing multi-component workloads from being rescheduled during cluster failover events. ([#7130](https://github.com/karmada-io/karmada/pull/7130), @mszacillo)
  • - karmada-webhook: Fixed an issue where the condition.reason was not set to QuotaExceeded when FederatedResourceQuota is exceeded. ([#7098](https://github.com/karmada-io/karmada/pull/7098), @kajal-jotwani)
  • - karmadactl: Fixed the messy auto-completion suggestions for commands like 'get' and 'apply'. ([#7025](https://github.com/karmada-io/karmada/pull/7025), @zhzhuang-zju)
  • - karmada-controller-manager: Fixed the issue where PP/CPP cannot be deleted because the resources API selected by the PP/CPP do not exist on the control plane. ([#7028](https://github.com/karmada-io/karmada/pull/7028), @XiShanYongYe-Chang)
  • - karmada-controller-manager: Fixed the issue that HelmRelease did not define observedGeneration variable in the statusAggregation operation. ([#7059](https://github.com/karmada-io/karmada/pull/7059), @FAUST-BENCHOU)
  • Fixed the issue that rbSpec.Components is not updated when the template is updated.
  • Fixed the Job status cannot be aggregated issue due to the missing JobSuccessCriteriaMet condition when using kube-apiserver v1.32+ as Karmada API server.
  • Fixed the issue that attached resource changes were not synchronized to the cluster in the dependencies distributor.
  • Fixed a panic when querying node metrics by name caused by using the wrong GroupVersionResource (PodsGVR instead of NodesGVR) when creating a lister.
  • Fixed the issue that CRDs cannot be updated during upgrades of the Karmada instance.
  • Fixed the issue where increasing the total number of replicas can cause some clusters to receive fewer replicas under the StaticWeight strategy by introducing the Webster algorithm.
  • Fixed the issue that resourcebinding validating webhook may panic when ReplicaRequirements of a Component in rbSpec.Components is nil.
  • Fixed the issue that the register command still uses the cluster-info endpoint when registering a pull-mode cluster, even if the user provides the API server endpoint.
  • Fixed the issue that when an object API field name contains dots or colons, it would cause the resource interpreter to fail.
  • karmadactl: Fixed the issue that the register command still uses the cluster-info endpoint when registering a pull-mode cluster, even if the user provides the API server endpoint.
  • karmada-metrics-adapter: Fixed a panic when querying node metrics by name caused by using the wrong GroupVersionResource (PodsGVR instead of NodesGVR) when creating a lister.
  • karmada-scheduler: Fixed the issue where increasing the total number of replicas can cause some clusters to receive fewer replicas under the StaticWeight strategy by introducing the Webster algorithm.
  • karmada-controller-manager: Fixed the issue that rbSpec.Components is not updated when the template is updated.
  • ResourceInterpreter: Fixed the issue that when an object API field name contains dots or colons, it would cause the resource interpreter to fail.
  • karmada-webhook: Fixed the issue that resourcebinding validating webhook may panic when ReplicaRequirements of a Component in rbSpec.Components is nil.
  • karmada-operator: Fixed the issue that CRDs can not be updated during upgrades of the Karmada instance.

additions (37)

  • In Karmada v1.16.0, we introduce **multi-component scheduling**, a new capability that enables the **complete and unified placement of multi-component workloads**—those composed of multiple interrelated components (e.g., jobManager and taskManagers of FlinkDeployment)—**into a single member cluster with sufficient resources**.
  • - Estimate how many full sets of components can fit into a member cluster based on **ResourceQuota** limits.
  • This release introduces an eviction queue with rate limiting capabilities for the Karmada taint manager. The eviction queue enhances the failover mechanism by controlling the rate of resource evictions using a configurable fixed rate parameter. The implementation also provides metrics for monitoring the eviction process, improving overall system observability.
  • - **Configurable Fixed Rate Limiting**: Configure the eviction rate per second through the --eviction-rate command-line flag.
  • - **Comprehensive Metrics Support**: Provides metrics for queue depth, resource kind, processing latency, and success/failure rates for monitoring and troubleshooting. By introducing the rate limiting mechanism, administrators can better control resource scheduling efficiency during cluster failover, balancing service stability with scheduling flexibility and efficiency.
  • Introduced Components field to ResourceInterpreterContext in the ResourceInterpreterResponse to support interpreting components for webhook interpreter.
  • Introduced a PodDisruptionBudget field to the CommonSettings of Karmada API for supporting PodDisruptionBudgets (PDBs) for Karmada control plane components.
  • The init command now supports customizing Karmada component command line flags.
  • The init command now supports customizing Karmada component command line flags via the configuration file.
  • Introduced built-in interpreter for Volcano Job.
  • Introduced a built-in interpreter for Kubeflow Notebooks.
  • Introduced built-in interpreter for SparkApplication.
  • Introduced built-in interpreter for PyTorchJob.
  • Introduced built-in resource interpreter for Kubernetes ReplicaSet workloads.
  • Introduced built-in interpreter for MPIJob.
  • Introduced --resource-eviction-rate flag to specify the eviction rate during cluster failover.
  • Implemented MaxAvailableComponentSets interface for general estimator based on resource summary.
  • Enabled the capability for multiple component estimation in the scheduler. The feature is gated behind MultiplePodTemplatesScheduling.
  • Implemented getMaximumSetsBasedOnResourceModels in general estimator.
  • Introduced MaxAvailableComponentSetsRequest & MaxAvailableComponentSetsResponse for component scheduling.
  • Added plugins in estimator for component scheduling.
  • Added ResourceQuota plugin for multi-component scheduling.
  • Implemented maxAvailableComponentSets for the accurate estimator.
  • Implemented the noderesource plugin for multi-component scheduling estimation.
  • Enabled federated resource quota calculation for multi-component scheduling.
  • Enabled GetComponents interpreter operation through Webhook Interpreter.
  • Added maxAvailableComponentSets to estimator interface.
  • Added PodDisruptionBudget (PDB) support to enable high availability guarantees for all control plane components during planned disruptions.
  • Added a new Warning event DependencyPolicyConflict to surface when dependency policies have conflicts.
  • Added new metrics for the failover eviction queue to enhance observability.
  • karmadactl: The init command now supports customizing Karmada component command line flags.
  • karmada-scheduler-estimator: Introduce MaxAvailableComponentSetsRequest & MaxAvailableComponentSetsResponse for component scheduling.
  • karmada-scheduler: Implemented MaxAvailableComponentSets interface for general estimator based on resource summary.
  • ResourceInterpreter: Enable GetComponents interpreter operation through Webhook Interpreter.
  • ResourceInterpreter: Adding maxAvailableComponentSets to estimator interface.
  • Helm chart: Added helm index for 1.15 release.
  • Multi-component scheduling is **disabled by default**.

value changes (19)

  • - The base image alpine has now been promoted from alpine:3.23.2 to alpine:3.23.3. ([#7162](https://github.com/karmada-io/karmada/pull/7162), @dependabot)
  • - The base image alpine has been promoted from alpine:3.22.2 to alpine:3.23.0. ([#7004](https://github.com/karmada-io/karmada/pull/7004), @dependabot)
  • - The base image alpine has been promoted from alpine:3.23.0 to alpine:3.23.2. ([#7037](https://github.com/karmada-io/karmada/pull/7037), @dependabot)
  • - **Monotonic replica assignment**: Increasing the total replica count will never cause any cluster to lose replicas, ensuring consistent and intuitive behavior.
  • - **Fair handling of remainder replicas**: When distributing replicas among clusters with equal weights, priority is given to the cluster with fewer current replicas. This "smaller-first" approach promotes balanced deployment and better satisfies high availability (HA) requirements. This update enhances the stability, fairness, and predictability of workload distribution across clusters, making replica scheduling more robust in multi-cluster environments.
  • For controllers not built on controller-runtime, such as the detector controller, we extend this capability in release-1.16 by enabling the priority-queue functionality for all controllers that use async workers. **Now, we can achieve downtime reduction for all controllers after a restart or leader transition.**
  • Computed effective field values for attached ResourceBindings when referenced by multiple ResourceBindings.
  • Migrated dynamic weight assignment to use the Webster algorithm.
  • Refactored the replica estimation logic by moving the node resource-based calculation into a dedicated, default plugin.
  • Karmada is now built with Golang ….×2
  • Kubernetes dependencies have been updated to v1.34.1.
  • Updated sigs.k8s.io/controller-runtime from v0.21.0 to v0.22.4.
  • The base image alpine has been promoted from 3.22.1 to 3.22.2.
  • After enabling the ControllerPriorityQueue feature gate, the asyncWorker uses a priority queue based implementation, which affects the processing order of items in the resource detector and causes the monitoring metric workqueue_depth to be split into multiple series.
  • The ControllerPriorityQueue feature gate now applies to all controllers, including async workers. Enable it with --feature-gates=ControllerPriorityQueue=true.
  • The base image alpine now has been promoted from 3.22.1 to 3.22.2.
  • Introduced Components field to ResourceInterpreterContext in the ResourceInterpreterResponse to support interpreting components for webhook interpreter.
  • we introduce the Webster method

constraints (8)

  • - Predict schedulability using **actual node resource availability** across clusters. Karmada v1.16.0 ships with built-in **resource interpreters** for the following multi-component workload types:
  • - FlinkDeployment (flink.apache.org/v1beta1/FlinkDeployment)
  • - SparkApplication (sparkoperator.k8s.io/v1beta2/SparkApplication)
  • - Volcano Job (batch.volcano.sh/v1alpha1/Job)
  • - MPIJob (kubeflow.org/v2beta1/MPIJob)
  • - RayCluster (ray.io/v1/RayCluster)
  • - RayJob (ray.io/v1/RayJob)
  • - TFJob (kubeflow.org/v1/TFJob)

defaults (2)

  • The init command's default kube-apiserver and kube-controller-manager images have been updated from v1.31.3 to v1.34.1. And the default etcd image has been updated from 3.5.16-0 to 3.6.0-0.
  • The default kube-apiserver and kube-controller-manager images have been updated from v1.31.3 to v1.34.1. The default etcd Image has been updated from 3.5.16-0 to 3.6.0-0.
Karmadaをスタックに追加

対応が必要なリリースが出たときに、週次メールでお知らせします。 今回のセキュリティパッチと破壊的変更も、その一例です。

スタックに追加 →
公式リリースノート ↗Karmadaのリリース一覧 →