Karmada
v1.17.2Orchestration & ManagementKarmada v1.17.2 is a patch release fixing scheduler misrouting bugs, operator reconciliation failures, and a Job replica assignment error — plus an Alpine base image bump for security.
breakingScheduler backoffQ misrouting may have masked real scheduling failures
Bindings with insufficient cluster replicas were incorrectly queued in backoffQ instead of unschedulableBindings. This means your scheduler may have been retrying workloads on an exponential backoff schedule rather than surfacing them as unschedulable. After upgrading, expect some previously silent failures to become visible in unschedulableBindings — review any workloads that seemed stuck or slow to schedule.
securityRebuild or pull updated images to get the Alpine 3.23.4 base
The base image was bumped from Alpine 3.23.3 to 3.23.4. If you're running air-gapped or mirrored image setups, make sure to pull and mirror the new v1.17.2 images. Check Alpine's changelog for the specific CVEs addressed if your compliance process requires it.
enhancementUpgrade if you use karmada-operator with custom tolerations/affinity or multi-cluster Jobs
Two high-impact fixes landed here: operator-managed deployments were silently ignoring tolerations and affinity configs, which could cause pods to land on unintended nodes. And Job completion counts were being assigned incorrectly across clusters, which could corrupt Job semantics in distributed workloads. Both are straightforward regressions worth patching immediately if either feature is in use.
Key changes (6)
- karmada-operator now correctly applies tolerations and affinity settings to karmada-aggregated-apiserver and karmada-search deployments
- Fixed non-idempotent secret creation that caused operator init reconciliation failures on repeated runs
- Scheduler no longer misroutes bindings with insufficient replicas to backoffQ — they now correctly land in unschedulableBindings
- Schedule success events with ClusterAffinities now include proper cluster information
- Job completions are now distributed correctly across clusters instead of being assigned to wrong replicas
- Base Alpine image bumped from 3.23.3 to 3.23.4 to address security concerns