RATATOSKRATATOSK
Sign in

Releases

AI-analyzed release notes for CNCF graduated and incubating projects.

May 2026Clear ×Project: KarmadaClear ×
Karmadav1.17.3Orchestration & ManagementMay 30, 2026

Karmada v1.17.3 is a maintenance release focused on operator-relevant bug fixes. The remaining release material consists of headings without standalone operator-facing changes.

Source
Karmadav1.16.6Orchestration & ManagementMay 30, 2026

Karmada v1.16.6 is a maintenance release with operator-focused bug fixes. The note tail indicates fixes in cluster resource watching, scheduling under resource pressure, and transient cluster client failures, with no disclosed security advisories or security-specific fixes.

Source
Karmadav1.15.9Orchestration & ManagementMay 30, 2026

Karmada v1.15.9 is a bug-fix release for operator-facing behavior. It addresses delayed resource reflection after recovered clusters reconnect in karmada-search and prevents transient ClusterClientSetFunc failures from immediately setting a cluster to Ready=False in karmada-controller-manager.

Source
Karmadav1.18.0Orchestration & ManagementMay 30, 2026

A feature and maintenance release that adds overflow scheduling and scheduling overcommit protection, along with API, default, constraint, metric, and flag changes. It also includes a security-related alpine base-image update and numerous defect corrections.

Action needed (1)

  • securityThe alpine base image update

    The alpine base image has changed from alpine:3.23.3 to alpine:3.23.4 to address security concerns.

Check if affected (9)

  • breakingThe overflowAffinities field

    Applies if you configure overflowAffinities.

    Users can declare supplementary cluster groups with the overflowAffinities field in a ClusterAffinityTerm.

  • breakingStricter clusterTolerations operator validation

    Applies if you set spec.placement.clusterTolerations with Lt or Gt.

    PropagationPolicy and ClusterPropagationPolicy resources that use the Lt or Gt operator are now rejected.

  • breakingThe operator's default verbosity level

    Applies if you run the operator.

    The operator now sets the default verbosity level to 2 for the specified components.

  • + 6 more on the release page
Source
Browse by month