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

Jun 2026Clear ×Project: StrimziClear ×

Strimzi1.1.0Networking & MessagingJun 27, 2026

CHECK 3OTHER 21View full analysis

This release adds operator-facing configuration and feature capabilities while updating supported Apache Kafka versions and related integrations. It also changes TLS file handling for KafkaBridge and KafkaMirrorMaker2 and renames entity-operator healthcheck ports, so those areas may require attention.

Check if affected (3)

breakingSupport for Kafka 4.1.x removed
Applies if you use Kafka 4.1.x.
Support for Kafka 4.1.x is removed in this release.
breakingPEM-based TLS files for KafkaBridge and KafkaMirrorMaker2
Applies if you use KafkaBridge or KafkaMirrorMaker2 with TLS authentication or a TLS truststore.
KafkaBridge and KafkaMirrorMaker2 now use PEM files instead of P12/JKS for TLS authentication and TLS truststores.
breakingEntity-operator healthcheck port names
Applies if you use entity-operator healthcheck ports.
The entity-operator healthcheck port names change from healthcheck to healthcheck-to for the topic operator and healthcheck-uo for the user operator.

Source ↗

Strimzi1.0.1Networking & MessagingJun 17, 2026

ACTION 2CHECK 2View full analysis

A release focused on CRD compatibility and Entity Operator watching defaults, with fixes for disclosed security vulnerabilities. It affects deployments using older CRD APIs or configuring cross-namespace watching.

Action needed (2)

securityhighFix for CVE-2026-55225
The release fixes CVE-2026-55225, also identified as GHSA-mw9r-p8xp-wx96.
securitymediumFix for CVE-2026-55226
The release fixes CVE-2026-55226, also identified as GHSA-r427-j2h7-wv3m.

Check if affected (2)

breakingSupported CRD API versions narrowed
Applies if you use the v1beta2, v1beta1, or v1alpha1 CRD APIs.
Only the new v1 CRD API is supported. The older v1beta2, v1beta1, and v1alpha1 APIs are no longer supported.
breakingEntity Operator cross-namespace watching default
Applies if you configure STRIMZI_ENTITY_OPERATOR_WATCHED_NAMESPACE_ENABLED or watchedNamespace.
Entity Operator cross-namespace watching is controlled by the STRIMZI_ENTITY_OPERATOR_WATCHED_NAMESPACE_ENABLED environment variable in the Cluster Operator. The feature is disabled by default.

Source ↗

Browse by month