Karmada
v1.15.8Orchestration & ManagementKarmada v1.15.8 is a targeted bug-fix patch addressing scheduler queue misrouting, missing cluster info in events, and an operator reconciliation failure. Alpine base image bumped for security.
breakingScheduler queue misrouting can cause workloads to be stuck — patch immediately
The backoffQ bug is particularly dangerous in production: when a binding hits insufficient replicas, it gets retried with exponential backoff instead of being placed in unschedulableBindings where it belongs. This means your workloads silently wait longer than expected before rescheduling. If you're running ClusterAffinities with replica constraints, upgrade to v1.15.8 — don't wait on this one.
securityRebuild and redeploy to pick up alpine:3.23.4 patches
The alpine base image bump from 3.23.3 to 3.23.4 addresses unspecified security concerns. If you're running custom Karmada images built from the upstream base, rebuild against the new base. If you're using official images, pulling v1.15.8 is sufficient.
enhancementOperator idempotency fix prevents init reconciliation crashes on restarts
The non-idempotent secret creation in karmada-operator meant that if the operator restarted mid-initialization, reconciliation would fail. This is now fixed with an idempotent approach. If you've been seeing operator init failures after pod restarts or rolling updates, this patch resolves the root cause.
主な変更 (4)
- karmada-operator: Fixed non-idempotent secret creation that caused init reconciliation failures on retry
- karmada-scheduler: Schedule success events now include cluster information when using ClusterAffinities
- karmada-scheduler: Bindings with insufficient cluster replicas now correctly land in unschedulableBindings queue instead of backoffQ
- Base image updated from alpine:3.23.3 to alpine:3.23.4 to address security concerns