Releases

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

URGENCY

All Action needed Check if affected Plan ahead

KIND

Category

All AI & ML CI/CD & App Delivery Kubernetes Core Networking & Messaging Observability Orchestration & Management Provisioning & Runtime Security Storage & Data

Project: StrimziClear ×

Strimzi1.2.0Networking & MessagingAug 20, 2026

ACTION 2CHECK 3OTHER 7View full analysis

This release removes legacy CRD API versions and resource state metrics, and changes defaults for token mounting, feature gates, and container security contexts. It also adds Kafka and configuration capabilities and updates shipped dependencies.

Action needed (2)

breakingService Account token mounting
Service Account tokens are no longer auto-mounted into Pods. They are mounted through a volume instead.
breakingThe ServerSideApplyPhase1 feature gate, permanently enabled
The ServerSideApplyPhase1 feature gate has moved to GA and is permanently enabled. It can no longer be disabled.

Check if affected (3)

breakingLegacy CRD API versions, no longer supported
Applies before upgrading to Strimzi 1.0.0 or later if you use the v1beta2, v1beta1, or v1alpha1 APIs.
Strimzi 1.0.0 and later support only the v1 CRD API. The older v1beta2, v1beta1, and v1alpha1 APIs are no longer supported.
breakingResource state metrics, removed
Applicability is not stated in the release notes.
Deprecated resource state metrics have been removed. The kube-state-metrics project should be used instead.
breakingDefault securityContext for operator installations
Applies if you use the Cluster, Topic, and User Operator YAML installation files or the Cluster Operator Helm Chart.
The Cluster, Topic, and User Operator YAML installation files and the Cluster Operator Helm Chart now use a default container security context that matches the Restricted Kubernetes Pod Security Standard. The default can be overridden with the securityContext property in the YAML installation files or Cluster Operator Helm Chart values.

Source ↗

Strimzi1.0.0Networking & MessagingApr 28, 2026

ACTION 2CHECK 4OTHER 12View full analysis

A release that removes older CRD API versions, changes defaults and configuration locations, and adds Kafka and HTTP Bridge capabilities. Monitoring configurations and standalone Topic Operator setups may require updates.

Action needed (2)

breakingThe UseConnectBuildWithBuildah feature gate, enabled by default
The UseConnectBuildWithBuildah feature gate moves to the beta stage and is enabled by default.
breakingThe /metrics endpoint, moved to the HTTP management interface
The /metrics endpoint is no longer available on the regular HTTP interface, which uses port 8080 by default. It is now available on the HTTP management interface on port 8081.

Check if affected (4)

breakingOlder CRD API versions, removed
Applies if you use the v1beta2, v1beta1, or v1alpha1 CRD APIs.
Strimzi 1.0.0 supports only the new v1 CRD API. The older v1beta2, v1beta1, and v1alpha1 APIs are no longer supported.
breakingThe Open Policy Agent (OPA) authorizer plugin, no longer bundled
Applies if you use the Open Policy Agent (OPA) authorizer plugin.
The Open Policy Agent (OPA) authorizer plugin is no longer bundled in Strimzi container images. It can be added as a custom plugin by building a custom Kafka container image or using additional volumes.
breakingLegacy TLS environment variables, ignored
Applies if you set any of STRIMZI_TLS_ENABLED, STRIMZI_TLS_AUTH_ENABLED, STRIMZI_PUBLIC_CA, STRIMZI_TRUSTSTORE_LOCATION, STRIMZI_TRUSTSTORE_PASSWORD, STRIMZI_KEYSTORE_LOCATION, or STRIMZI_KEYSTORE_PASSWORD.
The environment variables STRIMZI_TLS_ENABLED, STRIMZI_TLS_AUTH_ENABLED, STRIMZI_PUBLIC_CA, STRIMZI_TRUSTSTORE_LOCATION, STRIMZI_TRUSTSTORE_PASSWORD, STRIMZI_KEYSTORE_LOCATION, and STRIMZI_KEYSTORE_PASSWORD are no longer used and are ignored if set.
+ 1 more on the release page

Source ↗

Strimzi0.51.0Networking & MessagingMar 6, 2026

ACTION 2CHECK 2PLAN 1OTHER 2View full analysis

A release with fixes for two disclosed security vulnerabilities, updated Kubernetes and Kafka support, and a changed feature-gate default. It also adds Kafka 4.2.0 support and per-listener Kafka options, while the ingress listener type is deprecated; CRD upgrades and a KafkaUser field migration are upgrade prerequisites.

Action needed (2)

securityhighCVE-2026-27133 and CVE-2026-27134 security fixes
Security fixes in Strimzi 0.50.1 and 0.51.0 address CVE-2026-27133 and CVE-2026-27134, with advisories GHSA-2qwx-rq6j-8r6j and GHSA-6x85-j2f7-4xc5.
breakingThe ServerSideApplyPhase1 feature gate default
The ServerSideApplyPhase1 feature gate moved to beta and is enabled by default.

Check if affected (2)

breakingKubernetes version support
Applies if you use Kubernetes 1.27, 1.28, or 1.29.
Support is limited to Kubernetes 1.30 and newer. Kubernetes 1.27, 1.28, and 1.29 are no longer supported.
breakingKafka 4.0.0 and 4.0.1 support
Applies if you use Kafka 4.0.0 or 4.0.1.
Support for Kafka 4.0.0 and 4.0.1 is removed.

Plan ahead (1)

deprecatedThe ingress listener type deprecation
Applies if you configure the ingress listener type.
The ingress listener type is deprecated because the Ingress NGINX Controller for Kubernetes was archived.

Source ↗

Browse by month