Karmada
v1.19.0Orchestration & ManagementAug 31, 2026
A focused maintenance release removes obsolete API enum values and improves credential-watch reliability, scheduling behavior, and standalone scheduler-estimator installation. It contains no security changes.
Check if affected (1)
breakingDeprecated
PurgeModevalues, removedApplies if your API configuration uses
ImmediatelyorGraciously.The Karmada API removes the deprecated
PurgeModevaluesImmediatelyandGraciously. Configurations should useDirectlyandGracefullyinstead.
All 3 other recorded changesadditions 1 · fixes 1 · value changes 1
additions (1)
- -
karmada-controller-manager: Added support for automatically refreshing member cluster credentials for push-mode informers, ensuring long-lived resource watches continue working after token rotation. ([#7663](https://github.com/karmada-io/karmada/pull/7663), @zhuyulicfc49)
fixes (1)
- -
karmada-scheduler-estimator: Fixed the issue that installingschedulerEstimatoras a standalone component (installMode: component) failed to mount its certificate Secret because the Secret name was derived from the component release name instead of the host-mode release that created it. AddedschedulerEstimator.(defaultcerts karmada-cert) to configure the Secret name explicitly. ([#7815](https://github.com/karmada-io/karmada/pull/7815), @pujitha24)
value changes (1)
- -
karmada-scheduler: Moved bindings whose backoff or unschedulable timeout completed into the active queue in priority order within a single flush, so higher-priority bindings were retried first on a best-effort basis. ([#7814](https://github.com/karmada-io/karmada/pull/7814), @CaesarTY)
Add Karmada to your stack
A weekly email arrives when a release needs action. Like the breaking changes in this release.