<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Confluent for Kubernetes Release Notes</title><link>https://docs.confluent.io/operator/3.1/release-notes.html</link><description>Latest features and updates for Confluent for Kubernetes</description><language>en-us</language><lastBuildDate>Wed, 18 Nov 2026 16:12:25 GMT</lastBuildDate><ttl>180</ttl><copyright>Copyright © Confluent Inc.</copyright><atom:link href="https://docs.confluent.io/operator/3.1/release-notes.xml" rel="self" type="application/rss+xml"/><item><title>[25 September, 2026] Confluent for Kubernetes 3.1.4 Release Notes</title><link>https://docs.confluent.io/operator/3.1/release-notes.html#september-2026-co-long-3-1-4-release-notes</link><guid>https://docs.confluent.io/operator/3.1/release-notes.html#september-2026-co-long-3-1-4-release-notes</guid><pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate><description><![CDATA[ <span id="co-rn-3-1-4"></span> <section id="compatibility-and-container-images"> <h3>Compatibility and container images<a class="headerlink" href="#compatibility-and-container-images" title="Link to this heading"></a></h3> <p>CFK 3.1.x lets you deploy and manage Confluent Platform versions 7.3.x to 8.1.x on Kubernetes versions 1.26 - 1.34 (OpenShift 4.13 - 4.20).</p> <p>The images released in CFK 3.1.4 are:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-operator:0.1351.220</span></code></p></li> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-init-container:3.1.4</span></code></p></li> </ul> </section> <section id="breaking-changes"> <h3>Breaking changes<a class="headerlink" href="#breaking-changes" title="Link to this heading"></a></h3> <p>There are no breaking changes in this release.</p> </section> <section id="new-features"> <h3>New features<a class="headerlink" href="#new-features" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Adds <code class="docutils literal notranslate"><span class="pre">kubectl</span> <span class="pre">confluent</span> <span class="pre">block-reconcile</span></code> and <code class="docutils literal notranslate"><span class="pre">kubectl</span> <span class="pre">confluent</span>
<span class="pre">enable-reconcile</span></code> plugin commands. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-plugin-cli/kubectl_confluent_block-reconcile.html#kubectl-confluent-block-reconcile"><span class="std std-ref">kubectl confluent block-reconcile</span></a> and <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-plugin-cli/kubectl_confluent_enable-reconcile.html#kubectl-confluent-enable-reconcile"><span class="std std-ref">kubectl confluent enable-reconcile</span></a>.</p></li> </ul> </section> <section id="enhancements"> <h3>Enhancements<a class="headerlink" href="#enhancements" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Removes hard-coded <code class="docutils literal notranslate"><span class="pre">ParallelGCThreads=1</span></code> or <code class="docutils literal notranslate"><span class="pre">ConcGCThreads=1</span></code> JVM defaults. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-configure-misc.html#co-default-jvm-settings"><span class="std std-ref">Default JVM settings</span></a>.</p></li> <li><p>Enables FIPS on the Kafka broker and applies FIPS JVM settings through <code class="docutils literal notranslate"><span class="pre">jvm.config</span></code>.</p></li> <li><p>Adds <code class="docutils literal notranslate"><span class="pre">InternalClientConfig</span></code> override support for the operator’s internal Kafka client. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-network-encryption.html#co-disable-internal-client-hostname-verification"><span class="std std-ref">Disable TLS hostname verification for the Kafka internal client</span></a>.</p></li> <li><p>Checks Schema Registry status directly instead of trusting a cached configuration hash.</p></li> <li><p>Makes the Kafka-to-LDAP TLS client FIPS-aware using a Bouncy Castle FIPS Keystore (BCFKS).</p></li> <li><p>Removes stale multi-region cluster (MRC) bypass-prechecks guidance, a follow-up to the ZooKeeper <code class="docutils literal notranslate"><span class="pre">chroot</span></code> fix below.</p></li> </ul> </section> <section id="bug-fixes"> <h3>Bug fixes<a class="headerlink" href="#bug-fixes" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Fixed Jolokia configuration options not rendering as a single comma-separated line.</p></li> <li><p>Fixed the default ZooKeeper <code class="docutils literal notranslate"><span class="pre">chroot</span></code> to root during KRaft migration for MRC endpoints.</p></li> <li><p>Fixed the <code class="docutils literal notranslate"><span class="pre">KafkaTopic</span></code> controller so it keeps retrying replication factor (RF) fetches after a transient failure, instead of giving up permanently. The bug left <code class="docutils literal notranslate"><span class="pre">status.replicas</span></code> empty for topics created with <code class="docutils literal notranslate"><span class="pre">spec.replicas</span></code> unset, and was most noticeable when creating many topics at once through Helm. Broker-side RF was always correct. Only the <code class="docutils literal notranslate"><span class="pre">KafkaTopic</span></code> status was affected.</p></li> <li><p>Fixed the Metadata Service (MDS) client <code class="docutils literal notranslate"><span class="pre">keystore</span></code> rendering for the <code class="docutils literal notranslate"><span class="pre">mtls</span></code> type without <code class="docutils literal notranslate"><span class="pre">sslClientAuthentication</span></code>.</p></li> <li><p>Fixed the Schema Registry <code class="docutils literal notranslate"><span class="pre">restConfig</span></code> bootstrap URL.</p></li> <li><p>Fixed <code class="docutils literal notranslate"><span class="pre">spec.tls.fips.enabled:</span> <span class="pre">true</span></code> not being applied to the embedded Kafka REST proxy’s Metadata Service (MDS) client TLS configuration, which was always generated as <code class="docutils literal notranslate"><span class="pre">JKS</span></code> instead of <code class="docutils literal notranslate"><span class="pre">BCFKS</span></code>. Manual <code class="docutils literal notranslate"><span class="pre">kafka.rest.client.ssl.*</span></code> configuration overrides are no longer needed to run FIPS and RBAC deployments together.</p></li> <li><p>Fixed Kafka-to-ZooKeeper TLS connections crash-looping under FIPS mode due to a missing BCFKS <code class="docutils literal notranslate"><span class="pre">keystore</span></code> or <code class="docutils literal notranslate"><span class="pre">truststore</span></code> configuration.</p></li> <li><p>Fixed a <code class="docutils literal notranslate"><span class="pre">java.security.properties</span></code> path typo that silently prevented FIPS enforcement from taking effect.</p></li> <li><p>Fixed reconcile errors and a stale cluster phase being hidden in <code class="docutils literal notranslate"><span class="pre">Kafka</span></code> status. Status, Kubernetes events, and broker logs now surface the actual failure reason and cluster phase instead of generic or missing messages. This helps diagnose and recover from issues faster.</p></li> <li><p>Fixed an unnecessary full cluster roll caused by a stale cached read of tracked secret versions.</p></li> <li><p>Fixed a per-role Kafka discovery override issue in Connect, ksqlDB, and <code class="docutils literal notranslate"><span class="pre">KafkaRestProxy</span></code>.</p></li> <li><p>Fixed the Replicator <code class="docutils literal notranslate"><span class="pre">mTLS</span></code> connector plugin version.</p></li> <li><p>Fixed an RBAC name collision between External-DNS and Ingress-Nginx.</p></li> <li><p>Fixed FIPS-prefixed Kafka clients missing <code class="docutils literal notranslate"><span class="pre">security.providers</span></code>.</p></li> <li><p>Fixed excessive LDAP load caused by each mirror topic independently triggering an OAuth token request. Tokens are now batched and cached, preventing LDAP overload at scale.</p></li> <li><p>Fixed Cluster Linking remote-auth secrets not mounting on Kafka brokers.</p></li> <li><p>Fixed a Schema resource that could report <code class="docutils literal notranslate"><span class="pre">status.appState:</span> <span class="pre">Created</span></code> without the schema actually being registered in Schema Registry, following a reconcile interrupted at a specific point. Affected resources now self-heal on the next reconcile.</p></li> <li><p>Fixed Kafka custom resource (CR) reconciliation failures caused by TLS secrets (for example, <code class="docutils literal notranslate"><span class="pre">services.kafkaRest</span></code> mTLS) that contained only <code class="docutils literal notranslate"><span class="pre">JKS</span></code> or <code class="docutils literal notranslate"><span class="pre">PKCS12</span></code> material. Only PEM-style secrets were supported.</p></li> <li><p>Fixed an operator memory leak caused by idle outbound HTTP connections that were never closed, which could cause gradual memory growth and potential <code class="docutils literal notranslate"><span class="pre">OOMKilled</span></code> restarts. Idle connections now close after a configurable timeout set by <code class="docutils literal notranslate"><span class="pre">CONFLUENT_OPERATOR_HTTP_IDLE_CONN_TIMEOUT</span></code>, which defaults to 90 seconds. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cfk.html#co-deployment-custom-vars"><span class="std std-ref">Deploy CFK with custom environment variables</span></a>.</p></li> <li><p>Fixed the default OpenID Connect (OIDC) session token expiry, increasing it from 90 seconds to 15 minutes.</p></li> <li><p>Fixed TLS handshake errors flooding Control Center Prometheus and Alertmanager logs, caused by Kubernetes health checks against TLS-enabled endpoints. Set <code class="docutils literal notranslate"><span class="pre">useProcNetPortCheck:</span> <span class="pre">true</span></code> under <code class="docutils literal notranslate"><span class="pre">spec.podTemplate.probe.readiness</span></code> or <code class="docutils literal notranslate"><span class="pre">spec.podTemplate.probe.liveness</span></code> on the <code class="docutils literal notranslate"><span class="pre">ControlCenter</span></code> CR to switch these health checks to a TLS-free method.</p></li> <li><p>Fixed an issue that prevented installing or pinning to a specific, non-latest, CFK version through the OpenShift OperatorHub. Each release now retains a direct upgrade link to its predecessor in the Red Hat operator catalog.</p></li> </ul> </section> <section id="known-limitations"> <h3>Known limitations<a class="headerlink" href="#known-limitations" title="Link to this heading"></a></h3> <p>There are no new known limitations in this release.</p> </section> <section id="deprecations"> <h3>Deprecations<a class="headerlink" href="#deprecations" title="Link to this heading"></a></h3> <p>There are no new deprecations in this release.</p> </section> ]]></description><content:encoded><![CDATA[ <span id="co-rn-3-1-4"></span> <section id="compatibility-and-container-images"> <h3>Compatibility and container images<a class="headerlink" href="#compatibility-and-container-images" title="Link to this heading"></a></h3> <p>CFK 3.1.x lets you deploy and manage Confluent Platform versions 7.3.x to 8.1.x on Kubernetes versions 1.26 - 1.34 (OpenShift 4.13 - 4.20).</p> <p>The images released in CFK 3.1.4 are:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-operator:0.1351.220</span></code></p></li> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-init-container:3.1.4</span></code></p></li> </ul> </section> <section id="breaking-changes"> <h3>Breaking changes<a class="headerlink" href="#breaking-changes" title="Link to this heading"></a></h3> <p>There are no breaking changes in this release.</p> </section> <section id="new-features"> <h3>New features<a class="headerlink" href="#new-features" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Adds <code class="docutils literal notranslate"><span class="pre">kubectl</span> <span class="pre">confluent</span> <span class="pre">block-reconcile</span></code> and <code class="docutils literal notranslate"><span class="pre">kubectl</span> <span class="pre">confluent</span>
<span class="pre">enable-reconcile</span></code> plugin commands. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-plugin-cli/kubectl_confluent_block-reconcile.html#kubectl-confluent-block-reconcile"><span class="std std-ref">kubectl confluent block-reconcile</span></a> and <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-plugin-cli/kubectl_confluent_enable-reconcile.html#kubectl-confluent-enable-reconcile"><span class="std std-ref">kubectl confluent enable-reconcile</span></a>.</p></li> </ul> </section> <section id="enhancements"> <h3>Enhancements<a class="headerlink" href="#enhancements" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Removes hard-coded <code class="docutils literal notranslate"><span class="pre">ParallelGCThreads=1</span></code> or <code class="docutils literal notranslate"><span class="pre">ConcGCThreads=1</span></code> JVM defaults. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-configure-misc.html#co-default-jvm-settings"><span class="std std-ref">Default JVM settings</span></a>.</p></li> <li><p>Enables FIPS on the Kafka broker and applies FIPS JVM settings through <code class="docutils literal notranslate"><span class="pre">jvm.config</span></code>.</p></li> <li><p>Adds <code class="docutils literal notranslate"><span class="pre">InternalClientConfig</span></code> override support for the operator’s internal Kafka client. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-network-encryption.html#co-disable-internal-client-hostname-verification"><span class="std std-ref">Disable TLS hostname verification for the Kafka internal client</span></a>.</p></li> <li><p>Checks Schema Registry status directly instead of trusting a cached configuration hash.</p></li> <li><p>Makes the Kafka-to-LDAP TLS client FIPS-aware using a Bouncy Castle FIPS Keystore (BCFKS).</p></li> <li><p>Removes stale multi-region cluster (MRC) bypass-prechecks guidance, a follow-up to the ZooKeeper <code class="docutils literal notranslate"><span class="pre">chroot</span></code> fix below.</p></li> </ul> </section> <section id="bug-fixes"> <h3>Bug fixes<a class="headerlink" href="#bug-fixes" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Fixed Jolokia configuration options not rendering as a single comma-separated line.</p></li> <li><p>Fixed the default ZooKeeper <code class="docutils literal notranslate"><span class="pre">chroot</span></code> to root during KRaft migration for MRC endpoints.</p></li> <li><p>Fixed the <code class="docutils literal notranslate"><span class="pre">KafkaTopic</span></code> controller so it keeps retrying replication factor (RF) fetches after a transient failure, instead of giving up permanently. The bug left <code class="docutils literal notranslate"><span class="pre">status.replicas</span></code> empty for topics created with <code class="docutils literal notranslate"><span class="pre">spec.replicas</span></code> unset, and was most noticeable when creating many topics at once through Helm. Broker-side RF was always correct. Only the <code class="docutils literal notranslate"><span class="pre">KafkaTopic</span></code> status was affected.</p></li> <li><p>Fixed the Metadata Service (MDS) client <code class="docutils literal notranslate"><span class="pre">keystore</span></code> rendering for the <code class="docutils literal notranslate"><span class="pre">mtls</span></code> type without <code class="docutils literal notranslate"><span class="pre">sslClientAuthentication</span></code>.</p></li> <li><p>Fixed the Schema Registry <code class="docutils literal notranslate"><span class="pre">restConfig</span></code> bootstrap URL.</p></li> <li><p>Fixed <code class="docutils literal notranslate"><span class="pre">spec.tls.fips.enabled:</span> <span class="pre">true</span></code> not being applied to the embedded Kafka REST proxy’s Metadata Service (MDS) client TLS configuration, which was always generated as <code class="docutils literal notranslate"><span class="pre">JKS</span></code> instead of <code class="docutils literal notranslate"><span class="pre">BCFKS</span></code>. Manual <code class="docutils literal notranslate"><span class="pre">kafka.rest.client.ssl.*</span></code> configuration overrides are no longer needed to run FIPS and RBAC deployments together.</p></li> <li><p>Fixed Kafka-to-ZooKeeper TLS connections crash-looping under FIPS mode due to a missing BCFKS <code class="docutils literal notranslate"><span class="pre">keystore</span></code> or <code class="docutils literal notranslate"><span class="pre">truststore</span></code> configuration.</p></li> <li><p>Fixed a <code class="docutils literal notranslate"><span class="pre">java.security.properties</span></code> path typo that silently prevented FIPS enforcement from taking effect.</p></li> <li><p>Fixed reconcile errors and a stale cluster phase being hidden in <code class="docutils literal notranslate"><span class="pre">Kafka</span></code> status. Status, Kubernetes events, and broker logs now surface the actual failure reason and cluster phase instead of generic or missing messages. This helps diagnose and recover from issues faster.</p></li> <li><p>Fixed an unnecessary full cluster roll caused by a stale cached read of tracked secret versions.</p></li> <li><p>Fixed a per-role Kafka discovery override issue in Connect, ksqlDB, and <code class="docutils literal notranslate"><span class="pre">KafkaRestProxy</span></code>.</p></li> <li><p>Fixed the Replicator <code class="docutils literal notranslate"><span class="pre">mTLS</span></code> connector plugin version.</p></li> <li><p>Fixed an RBAC name collision between External-DNS and Ingress-Nginx.</p></li> <li><p>Fixed FIPS-prefixed Kafka clients missing <code class="docutils literal notranslate"><span class="pre">security.providers</span></code>.</p></li> <li><p>Fixed excessive LDAP load caused by each mirror topic independently triggering an OAuth token request. Tokens are now batched and cached, preventing LDAP overload at scale.</p></li> <li><p>Fixed Cluster Linking remote-auth secrets not mounting on Kafka brokers.</p></li> <li><p>Fixed a Schema resource that could report <code class="docutils literal notranslate"><span class="pre">status.appState:</span> <span class="pre">Created</span></code> without the schema actually being registered in Schema Registry, following a reconcile interrupted at a specific point. Affected resources now self-heal on the next reconcile.</p></li> <li><p>Fixed Kafka custom resource (CR) reconciliation failures caused by TLS secrets (for example, <code class="docutils literal notranslate"><span class="pre">services.kafkaRest</span></code> mTLS) that contained only <code class="docutils literal notranslate"><span class="pre">JKS</span></code> or <code class="docutils literal notranslate"><span class="pre">PKCS12</span></code> material. Only PEM-style secrets were supported.</p></li> <li><p>Fixed an operator memory leak caused by idle outbound HTTP connections that were never closed, which could cause gradual memory growth and potential <code class="docutils literal notranslate"><span class="pre">OOMKilled</span></code> restarts. Idle connections now close after a configurable timeout set by <code class="docutils literal notranslate"><span class="pre">CONFLUENT_OPERATOR_HTTP_IDLE_CONN_TIMEOUT</span></code>, which defaults to 90 seconds. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cfk.html#co-deployment-custom-vars"><span class="std std-ref">Deploy CFK with custom environment variables</span></a>.</p></li> <li><p>Fixed the default OpenID Connect (OIDC) session token expiry, increasing it from 90 seconds to 15 minutes.</p></li> <li><p>Fixed TLS handshake errors flooding Control Center Prometheus and Alertmanager logs, caused by Kubernetes health checks against TLS-enabled endpoints. Set <code class="docutils literal notranslate"><span class="pre">useProcNetPortCheck:</span> <span class="pre">true</span></code> under <code class="docutils literal notranslate"><span class="pre">spec.podTemplate.probe.readiness</span></code> or <code class="docutils literal notranslate"><span class="pre">spec.podTemplate.probe.liveness</span></code> on the <code class="docutils literal notranslate"><span class="pre">ControlCenter</span></code> CR to switch these health checks to a TLS-free method.</p></li> <li><p>Fixed an issue that prevented installing or pinning to a specific, non-latest, CFK version through the OpenShift OperatorHub. Each release now retains a direct upgrade link to its predecessor in the Red Hat operator catalog.</p></li> </ul> </section> <section id="known-limitations"> <h3>Known limitations<a class="headerlink" href="#known-limitations" title="Link to this heading"></a></h3> <p>There are no new known limitations in this release.</p> </section> <section id="deprecations"> <h3>Deprecations<a class="headerlink" href="#deprecations" title="Link to this heading"></a></h3> <p>There are no new deprecations in this release.</p> </section> ]]></content:encoded></item><item><title>[23 June, 2026] Confluent for Kubernetes 3.1.3 Release Notes</title><link>https://docs.confluent.io/operator/3.1/release-notes.html#june-2026-co-long-3-1-3-release-notes</link><guid>https://docs.confluent.io/operator/3.1/release-notes.html#june-2026-co-long-3-1-3-release-notes</guid><pubDate>Tue, 23 Jun 2026 00:00:00 GMT</pubDate><description><![CDATA[ <section id="id1"> <h3>Compatibility and container images<a class="headerlink" href="#id1" title="Link to this heading"></a></h3> <p>CFK 3.1.x lets you deploy and manage Confluent Platform versions 7.3.x to 8.1.x on Kubernetes versions 1.26 - 1.34 (OpenShift 4.13 - 4.20).</p> <p>The images released in CFK 3.1.3 are:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-operator:0.1351.147</span></code></p></li> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-init-container:3.1.3</span></code></p></li> </ul> </section> <section id="id2"> <h3>New features<a class="headerlink" href="#id2" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Adds support for the migration pre-check utility for single-cluster KRaft migrations. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-migrate-kraft-procedure.html#co-migrate-kraft-enable-preflight-v2"><span class="std std-ref">Step 3.2: Enable the ZooKeeper metadata preflight check</span></a>.</p></li> <li><p>Locks Kafka, ZooKeeper, and KRaftController CRs during KRaft migration to prevent accidental modifications or deletions. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-migrate-kraft-prerequisites.html#co-migrate-kraft-enforce-cr-locks-v2"><span class="std std-ref">CR lock enforcement</span></a>.</p></li> <li><p>Supports KRaft migration rollback from the <code class="docutils literal notranslate"><span class="pre">SETUP</span></code> and <code class="docutils literal notranslate"><span class="pre">MIGRATE</span></code> phases (previously <code class="docutils literal notranslate"><span class="pre">DUAL-WRITE</span></code> only). See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-migrate-kraft-rollback.html#co-migrate-kraft-rollback-v2"><span class="std std-ref">Roll Back to ZooKeeper</span></a>.</p></li> <li><p>Adds <code class="docutils literal notranslate"><span class="pre">kubectl</span> <span class="pre">confluent</span> <span class="pre">cluster</span> <span class="pre">kraft-migration</span></code> plugin for managing KRaft migration lifecycle operations: status, finalize, rollback, and CR lock release. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-migrate-kraft-command-reference.html#co-migrate-kraft-plugin-commands-v2"><span class="std std-ref">KRaft Migration Plugin Commands</span></a>.</p></li> </ul> </section> <section id="id3"> <h3>Enhancements<a class="headerlink" href="#id3" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Validates <code class="docutils literal notranslate"><span class="pre">configOverrides.server</span></code> for blocklisted keys (for example, <code class="docutils literal notranslate"><span class="pre">zookeeper.connect</span></code>) before starting KRaft migration, and blocks migration with an actionable error on conflicts. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-migrate-kraft-procedure.html#co-migrate-kraft-deploy-migration-job-v2"><span class="std std-ref">Step 3: Start migration</span></a>.</p></li> <li><p>Improves Kafka and KRaft readiness probing to avoid probe-generated connection churn and false mTLS authentication failures from polluting operational metrics.</p></li> <li><p>Masks sensitive credentials in CFK log output through a centralized redaction wrapper, so plain-text credentials are sanitized before reaching any log sink.</p></li> </ul> </section> <section id="id4"> <h3>Bug fixes<a class="headerlink" href="#id4" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Fixed a multi-region KRaft migration issue where the KRaft controller required a manual override for the <code class="docutils literal notranslate"><span class="pre">zookeeper.connect</span></code> configuration.</p></li> <li><p>Fixed Schema Registry cluster discovery for external-access and multi-region deployments by handling multi-URL endpoints correctly when <code class="docutils literal notranslate"><span class="pre">schemaRegistryClusterRef</span></code> is used.</p></li> <li><p>Fixed a connector cleanup issue to ensure that CFK deletes connectors even if their creation returned an HTTP 500 error, preventing orphaned connectors from accumulating on the Connect cluster.</p></li> <li><p>Fixed incorrect <code class="docutils literal notranslate"><span class="pre">advertised.listeners</span></code> ports when multiple user-defined listeners share the same static or <code class="docutils literal notranslate"><span class="pre">nodePort</span></code> offset.</p></li> </ul> </section> <section id="id5"> <h3>Known limitations<a class="headerlink" href="#id5" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>The operator can leak memory and <code class="docutils literal notranslate"><span class="pre">goroutines</span></code> over time from idle outbound HTTP connections (to Kafka REST, Metadata Service (MDS), Schema Registry, or an OAuth identity provider) that are never closed. This can affect any deployment. Upgrade to CFK 3.1.4 or later, which adds a configurable idle-connection timeout to fix this. See <a class="reference internal" href="#co-rn-3-1-4"><span class="std std-ref">[25 September, 2026] Confluent for Kubernetes 3.1.4 Release Notes</span></a>.</p></li> </ul> </section> <section id="id6"> <h3>Deprecations<a class="headerlink" href="#id6" title="Link to this heading"></a></h3> <p>There are no new deprecations in this release.</p> </section> ]]></description><content:encoded><![CDATA[ <section id="id1"> <h3>Compatibility and container images<a class="headerlink" href="#id1" title="Link to this heading"></a></h3> <p>CFK 3.1.x lets you deploy and manage Confluent Platform versions 7.3.x to 8.1.x on Kubernetes versions 1.26 - 1.34 (OpenShift 4.13 - 4.20).</p> <p>The images released in CFK 3.1.3 are:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-operator:0.1351.147</span></code></p></li> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-init-container:3.1.3</span></code></p></li> </ul> </section> <section id="id2"> <h3>New features<a class="headerlink" href="#id2" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Adds support for the migration pre-check utility for single-cluster KRaft migrations. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-migrate-kraft-procedure.html#co-migrate-kraft-enable-preflight-v2"><span class="std std-ref">Step 3.2: Enable the ZooKeeper metadata preflight check</span></a>.</p></li> <li><p>Locks Kafka, ZooKeeper, and KRaftController CRs during KRaft migration to prevent accidental modifications or deletions. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-migrate-kraft-prerequisites.html#co-migrate-kraft-enforce-cr-locks-v2"><span class="std std-ref">CR lock enforcement</span></a>.</p></li> <li><p>Supports KRaft migration rollback from the <code class="docutils literal notranslate"><span class="pre">SETUP</span></code> and <code class="docutils literal notranslate"><span class="pre">MIGRATE</span></code> phases (previously <code class="docutils literal notranslate"><span class="pre">DUAL-WRITE</span></code> only). See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-migrate-kraft-rollback.html#co-migrate-kraft-rollback-v2"><span class="std std-ref">Roll Back to ZooKeeper</span></a>.</p></li> <li><p>Adds <code class="docutils literal notranslate"><span class="pre">kubectl</span> <span class="pre">confluent</span> <span class="pre">cluster</span> <span class="pre">kraft-migration</span></code> plugin for managing KRaft migration lifecycle operations: status, finalize, rollback, and CR lock release. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-migrate-kraft-command-reference.html#co-migrate-kraft-plugin-commands-v2"><span class="std std-ref">KRaft Migration Plugin Commands</span></a>.</p></li> </ul> </section> <section id="id3"> <h3>Enhancements<a class="headerlink" href="#id3" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Validates <code class="docutils literal notranslate"><span class="pre">configOverrides.server</span></code> for blocklisted keys (for example, <code class="docutils literal notranslate"><span class="pre">zookeeper.connect</span></code>) before starting KRaft migration, and blocks migration with an actionable error on conflicts. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-migrate-kraft-procedure.html#co-migrate-kraft-deploy-migration-job-v2"><span class="std std-ref">Step 3: Start migration</span></a>.</p></li> <li><p>Improves Kafka and KRaft readiness probing to avoid probe-generated connection churn and false mTLS authentication failures from polluting operational metrics.</p></li> <li><p>Masks sensitive credentials in CFK log output through a centralized redaction wrapper, so plain-text credentials are sanitized before reaching any log sink.</p></li> </ul> </section> <section id="id4"> <h3>Bug fixes<a class="headerlink" href="#id4" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>Fixed a multi-region KRaft migration issue where the KRaft controller required a manual override for the <code class="docutils literal notranslate"><span class="pre">zookeeper.connect</span></code> configuration.</p></li> <li><p>Fixed Schema Registry cluster discovery for external-access and multi-region deployments by handling multi-URL endpoints correctly when <code class="docutils literal notranslate"><span class="pre">schemaRegistryClusterRef</span></code> is used.</p></li> <li><p>Fixed a connector cleanup issue to ensure that CFK deletes connectors even if their creation returned an HTTP 500 error, preventing orphaned connectors from accumulating on the Connect cluster.</p></li> <li><p>Fixed incorrect <code class="docutils literal notranslate"><span class="pre">advertised.listeners</span></code> ports when multiple user-defined listeners share the same static or <code class="docutils literal notranslate"><span class="pre">nodePort</span></code> offset.</p></li> </ul> </section> <section id="id5"> <h3>Known limitations<a class="headerlink" href="#id5" title="Link to this heading"></a></h3> <ul class="simple"> <li><p>The operator can leak memory and <code class="docutils literal notranslate"><span class="pre">goroutines</span></code> over time from idle outbound HTTP connections (to Kafka REST, Metadata Service (MDS), Schema Registry, or an OAuth identity provider) that are never closed. This can affect any deployment. Upgrade to CFK 3.1.4 or later, which adds a configurable idle-connection timeout to fix this. See <a class="reference internal" href="#co-rn-3-1-4"><span class="std std-ref">[25 September, 2026] Confluent for Kubernetes 3.1.4 Release Notes</span></a>.</p></li> </ul> </section> <section id="id6"> <h3>Deprecations<a class="headerlink" href="#id6" title="Link to this heading"></a></h3> <p>There are no new deprecations in this release.</p> </section> ]]></content:encoded></item><item><title>[25 March, 2026] Confluent for Kubernetes 3.1.2 Release Notes</title><link>https://docs.confluent.io/operator/3.1/release-notes.html#march-2026-co-long-3-1-2-release-notes</link><guid>https://docs.confluent.io/operator/3.1/release-notes.html#march-2026-co-long-3-1-2-release-notes</guid><pubDate>Wed, 25 Mar 2026 00:00:00 GMT</pubDate><description><![CDATA[ <p>CFK 3.1.2 allows you to deploy and manage Confluent Platform versions from 7.4.x to 8.1.x on Kubernetes versions 1.26 - 1.34 (OpenShift 4.13 -4.20).</p> <p>The images released in CFK 3.1.2 are:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-operator:0.1351.103</span></code></p></li> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-init-container:3.1.2</span></code></p></li> </ul> <p>For details on installing CFK and Confluent Platform using the above images, see <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cfk.html#co-deploy-operator"><span class="std std-ref">Deploy Confluent for Kubernetes</span></a> and <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cp.html#co-deploy-cp"><span class="std std-ref">Deploy Confluent Platform using Confluent for Kubernetes</span></a>.</p> <section id="notable-fixes"> <h3>Notable fixes<a class="headerlink" href="#notable-fixes" title="Link to this heading"></a></h3> <ul> <li><p>Fixed an issue where the <code class="docutils literal notranslate"><span class="pre">platform.confluent.io/roll-delay-interval-seconds</span></code> annotation was ignored when upgrading the operator. This was causing pods to roll immediately instead of waiting for the configured delay.</p></li> <li><p>Fixed an issue where custom OAuth listeners failed to validate without JAAS configurations.</p></li> <li><p>Fixed connector reconciliation for masked sensitive fields in Connect.</p> <p>Updated CFK’s connector reconciliation logic to properly handle Connect’s credential masking in the REST API, preventing unnecessary connector updates or restarts when sensitive configuration fields are masked.</p> </li> <li><p>Added auto reconcile capability for cluster link.</p></li> <li><p>Improved validation for inter-broker protocol (IBP) version and added automatic derivation of IBP for standard Confluent Platform images.</p></li> <li><p>Fixed an issue where the Unified Stream Manager (USM) extension class was not being added when RBAC authorization was enabled.</p></li> <li><p>Fixed metrics TLS configuration to correctly resolve keystore passwords from Vault-injected files when using <code class="docutils literal notranslate"><span class="pre">DirectoryPathInContainer</span></code>.</p></li> <li><p>Added support for configuring JMX authentication and access control using CR specifications to secure exposed JMX ports for all Confluent Platform components.</p> <div class="admonition important" data-admonition-type="important" role="note"> <span aria-hidden="true" class="admonition-icon"></span><div class="admonition-content"><p class="admonition-title">Important</p> <p>This is a breaking change to secure exposed JMX ports. This affects existing deployments that access JMX ports remotely for metrics queries.</p> </div></div> <p>For more information, see <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-monitor-cp.html#co-monitor-jmx"><span class="std std-ref">JMX Metrics</span></a>.</p> </li> <li><p>For the list of security and vulnerability issues fixed in this release, see <a class="reference external" href="https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes">Security Advisories and Security Release Notes</a>.</p></li> </ul> </section> ]]></description><content:encoded><![CDATA[ <p>CFK 3.1.2 allows you to deploy and manage Confluent Platform versions from 7.4.x to 8.1.x on Kubernetes versions 1.26 - 1.34 (OpenShift 4.13 -4.20).</p> <p>The images released in CFK 3.1.2 are:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-operator:0.1351.103</span></code></p></li> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-init-container:3.1.2</span></code></p></li> </ul> <p>For details on installing CFK and Confluent Platform using the above images, see <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cfk.html#co-deploy-operator"><span class="std std-ref">Deploy Confluent for Kubernetes</span></a> and <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cp.html#co-deploy-cp"><span class="std std-ref">Deploy Confluent Platform using Confluent for Kubernetes</span></a>.</p> <section id="notable-fixes"> <h3>Notable fixes<a class="headerlink" href="#notable-fixes" title="Link to this heading"></a></h3> <ul> <li><p>Fixed an issue where the <code class="docutils literal notranslate"><span class="pre">platform.confluent.io/roll-delay-interval-seconds</span></code> annotation was ignored when upgrading the operator. This was causing pods to roll immediately instead of waiting for the configured delay.</p></li> <li><p>Fixed an issue where custom OAuth listeners failed to validate without JAAS configurations.</p></li> <li><p>Fixed connector reconciliation for masked sensitive fields in Connect.</p> <p>Updated CFK’s connector reconciliation logic to properly handle Connect’s credential masking in the REST API, preventing unnecessary connector updates or restarts when sensitive configuration fields are masked.</p> </li> <li><p>Added auto reconcile capability for cluster link.</p></li> <li><p>Improved validation for inter-broker protocol (IBP) version and added automatic derivation of IBP for standard Confluent Platform images.</p></li> <li><p>Fixed an issue where the Unified Stream Manager (USM) extension class was not being added when RBAC authorization was enabled.</p></li> <li><p>Fixed metrics TLS configuration to correctly resolve keystore passwords from Vault-injected files when using <code class="docutils literal notranslate"><span class="pre">DirectoryPathInContainer</span></code>.</p></li> <li><p>Added support for configuring JMX authentication and access control using CR specifications to secure exposed JMX ports for all Confluent Platform components.</p> <div class="admonition important" data-admonition-type="important" role="note"> <span aria-hidden="true" class="admonition-icon"></span><div class="admonition-content"><p class="admonition-title">Important</p> <p>This is a breaking change to secure exposed JMX ports. This affects existing deployments that access JMX ports remotely for metrics queries.</p> </div></div> <p>For more information, see <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-monitor-cp.html#co-monitor-jmx"><span class="std std-ref">JMX Metrics</span></a>.</p> </li> <li><p>For the list of security and vulnerability issues fixed in this release, see <a class="reference external" href="https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes">Security Advisories and Security Release Notes</a>.</p></li> </ul> </section> ]]></content:encoded></item><item><title>[8 December, 2025] Confluent for Kubernetes 3.1.1 Release Notes</title><link>https://docs.confluent.io/operator/3.1/release-notes.html#december-2025-co-long-3-1-1-release-notes</link><guid>https://docs.confluent.io/operator/3.1/release-notes.html#december-2025-co-long-3-1-1-release-notes</guid><pubDate>Mon, 08 Dec 2025 00:00:00 GMT</pubDate><description><![CDATA[ <p>CFK 3.1.1 allows you to deploy and manage Confluent Platform versions from 7.4.x to 8.1.x on Kubernetes versions 1.26 - 1.34 (OpenShift 4.13 -4.20).</p> <p>The images released in CFK 3.1.1 are:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-operator:0.1351.59</span></code></p></li> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-init-container:3.1.1</span></code></p></li> </ul> <p>For details on installing CFK and Confluent Platform using the above images, see <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cfk.html#co-deploy-operator"><span class="std std-ref">Deploy Confluent for Kubernetes</span></a> and <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cp.html#co-deploy-cp"><span class="std std-ref">Deploy Confluent Platform using Confluent for Kubernetes</span></a>.</p> <section id="id7"> <h3>Notable fixes<a class="headerlink" href="#id7" title="Link to this heading"></a></h3> <ul> <li><p>Fixed issues with renewing certificate authorities (CAs) for auto-generated certificates.</p> <p>See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-manage-certificates.html#co-manage-certificates"><span class="std std-ref">Manage TLS Certificates for Confluent Platform Using Confluent for Kubernetes</span></a>.</p> </li> <li><p>Added preventive validation in the CFK webhook for Kafka cluster scale-up and scale-down operations.</p></li> <li><p>Removed the inter-broker protocol version in Kafka server properties for KRaft-based clusters.</p></li> <li><p>Improved output of the KafkaRestClass custom resource (CR) status through <code class="docutils literal notranslate"><span class="pre">kubectl</span></code>.</p></li> <li><p>Fixed an issue in KRaft migration rollback to ZooKeeper where the required <code class="docutils literal notranslate"><span class="pre">platform.confluent.io/format-cluster-metadata-in-kafka</span></code> annotation was not being automatically added to the Kafka CR.</p></li> <li><p>Fixed node port collision for Kafka Token and TokenSASL listeners when using mTLS and RBAC in a Multi-Region Cluster (MRC) setup.</p></li> <li><p>Fixed load balancer port collision for Kafka Token and TokenSASL listeners when using mTLS and RBAC in a Multi-Region Cluster (MRC) setup.</p></li> <li><p>Now you can configure container security context for Control Center’s Prometheus and Alertmanager containers.</p></li> <li><p>Fixed an issue where only the Control Center Prometheus load balancer service was created when external access was enabled for both Control Center and Prometheus.</p></li> <li><p>Fixed GnuTLS security failures by falling back to <code class="docutils literal notranslate"><span class="pre">curl</span></code> if <code class="docutils literal notranslate"><span class="pre">wget</span></code> is unable to retrieve Connect plugins.</p></li> <li><p>Corrected the cluster role definition in OpenShift OperatorHub to match with the one in the Helm release.</p></li> <li><p>For the list of security and vulnerability issues fixed in this release, see <a class="reference external" href="https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes">Security Advisories and Security Release Notes</a>.</p></li> </ul> </section> ]]></description><content:encoded><![CDATA[ <p>CFK 3.1.1 allows you to deploy and manage Confluent Platform versions from 7.4.x to 8.1.x on Kubernetes versions 1.26 - 1.34 (OpenShift 4.13 -4.20).</p> <p>The images released in CFK 3.1.1 are:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-operator:0.1351.59</span></code></p></li> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-init-container:3.1.1</span></code></p></li> </ul> <p>For details on installing CFK and Confluent Platform using the above images, see <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cfk.html#co-deploy-operator"><span class="std std-ref">Deploy Confluent for Kubernetes</span></a> and <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cp.html#co-deploy-cp"><span class="std std-ref">Deploy Confluent Platform using Confluent for Kubernetes</span></a>.</p> <section id="id7"> <h3>Notable fixes<a class="headerlink" href="#id7" title="Link to this heading"></a></h3> <ul> <li><p>Fixed issues with renewing certificate authorities (CAs) for auto-generated certificates.</p> <p>See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-manage-certificates.html#co-manage-certificates"><span class="std std-ref">Manage TLS Certificates for Confluent Platform Using Confluent for Kubernetes</span></a>.</p> </li> <li><p>Added preventive validation in the CFK webhook for Kafka cluster scale-up and scale-down operations.</p></li> <li><p>Removed the inter-broker protocol version in Kafka server properties for KRaft-based clusters.</p></li> <li><p>Improved output of the KafkaRestClass custom resource (CR) status through <code class="docutils literal notranslate"><span class="pre">kubectl</span></code>.</p></li> <li><p>Fixed an issue in KRaft migration rollback to ZooKeeper where the required <code class="docutils literal notranslate"><span class="pre">platform.confluent.io/format-cluster-metadata-in-kafka</span></code> annotation was not being automatically added to the Kafka CR.</p></li> <li><p>Fixed node port collision for Kafka Token and TokenSASL listeners when using mTLS and RBAC in a Multi-Region Cluster (MRC) setup.</p></li> <li><p>Fixed load balancer port collision for Kafka Token and TokenSASL listeners when using mTLS and RBAC in a Multi-Region Cluster (MRC) setup.</p></li> <li><p>Now you can configure container security context for Control Center’s Prometheus and Alertmanager containers.</p></li> <li><p>Fixed an issue where only the Control Center Prometheus load balancer service was created when external access was enabled for both Control Center and Prometheus.</p></li> <li><p>Fixed GnuTLS security failures by falling back to <code class="docutils literal notranslate"><span class="pre">curl</span></code> if <code class="docutils literal notranslate"><span class="pre">wget</span></code> is unable to retrieve Connect plugins.</p></li> <li><p>Corrected the cluster role definition in OpenShift OperatorHub to match with the one in the Helm release.</p></li> <li><p>For the list of security and vulnerability issues fixed in this release, see <a class="reference external" href="https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes">Security Advisories and Security Release Notes</a>.</p></li> </ul> </section> ]]></content:encoded></item><item><title>[16 October, 2025] Confluent for Kubernetes 3.1.0 Release Notes</title><link>https://docs.confluent.io/operator/3.1/release-notes.html#october-2025-co-long-3-1-0-release-notes</link><guid>https://docs.confluent.io/operator/3.1/release-notes.html#october-2025-co-long-3-1-0-release-notes</guid><pubDate>Thu, 16 Oct 2025 00:00:00 GMT</pubDate><description><![CDATA[ <p>CFK 3.1.0 allows you to deploy and manage Confluent Platform versions from 7.3.x to 8.1.x on Kubernetes versions 1.26 - 1.34 (OpenShift 4.13 -4.19).</p> <p>The images released in CFK 3.1.0 are:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-operator:0.1351.24</span></code></p></li> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-init-container:3.1.0</span></code></p></li> </ul> <p>For details on installing CFK and Confluent Platform using the above images, see <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cfk.html#co-deploy-operator"><span class="std std-ref">Deploy Confluent for Kubernetes</span></a> and <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cp.html#co-deploy-cp"><span class="std std-ref">Deploy Confluent Platform using Confluent for Kubernetes</span></a>.</p> <section id="new-features-and-enhancements"> <h3>New features and enhancements<a class="headerlink" href="#new-features-and-enhancements" title="Link to this heading"></a></h3> <p>CFK 3.1.0 is a minor release with the following noteworthy new features and updates.</p> <dl> <dt>Confluent Unified Stream Manager Agent Support</dt><dd><p>You can use CFK to deploy Unified Stream Manager.</p> <p>See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-configure-usm.html#co-usm"><span class="std std-ref">Configure, Deploy, and Manage Unified Stream Manager Using Confluent for Kubernetes</span></a>.</p> </dd> <dt>Unified Stream Manager Schema Registry Support</dt><dd><p>You can use CFK to deploy Unified Stream Manager Schema Registry.</p> <p>See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-schema-registry-switchover.html#co-schema-registry-switchover"><span class="std std-ref">Set up Schema Registry Switchover with Unified Stream Manager</span></a>.</p> </dd> <dt>Confluent Private Cloud Gateway Support</dt><dd><p>You can use CFK to deploy Confluent Gateway.</p> <p>See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/gateway/co-gateway-overview.html#co-gateway-overview"><span class="std std-ref">Deploy and Manage Confluent Gateway with Confluent for Kubernetes</span></a>.</p> </dd> <dt>Removal of Confluent for Kubernetes (CFK) Blueprints</dt><dd><p>Confluent for Kubernetes (CFK) Blueprints (the <a class="reference external" href="https://hub.docker.com/r/confluentinc/cpc-operator">cpc-operator</a> image) is deprecated and removed in this release. The image is still available on Docker Hub for existing deployments but is no longer updated or patched for security vulnerabilities.</p> </dd> </dl> </section> <section id="notable-update"> <h3>Notable update<a class="headerlink" href="#notable-update" title="Link to this heading"></a></h3> <p>A new Confluent Enterprise license is available for the customer-managed Confluent Platform for Confluent Cloud subscription. This license allows you to use self-managed Confluent Platform components exclusively with Confluent Cloud services.</p> <p>If you encounter the following error when provisioning a new license, you should upgrade to a CFK version, 2.9.7, 2.10.3, 2.11.3, 3.0.1, 3.1.0, or later.</p> <div class="highlight-text notranslate"><div class="highlight"><pre><span></span>secretRef confluent-license: missing subject or contains invalid subject
</pre></div> </div> </section> <section id="known-issues"> <h3>Known issues<a class="headerlink" href="#known-issues" title="Link to this heading"></a></h3> <ul> <li><p>When deploying CFK to Red Hat OpenShift with Red Hat’s Operator Lifecycle Manager using the OperatorHub, you must use OpenShift version 4.9 or higher.</p> <p>This OpenShift version restriction does not apply when deploying CFK to Red Hat OpenShift in the standard way without using the Red Hat Operator Lifecycle Manager.</p> </li> <li><p>When CFK is deployed on an OpenShift cluster with Red Hat’s Operator LIfecycle Manager/OperatorHub, capturing the support bundle for CFK using the command, <code class="docutils literal notranslate"><span class="pre">kubectl</span> <span class="pre">confluent</span> <span class="pre">support-bundle</span> <span class="pre">--namespace</span> <span class="pre">&lt;namespace&gt;</span></code>, can fail with the following error message:</p> <div class="highlight-text notranslate"><div class="highlight"><pre><span></span>panic: runtime error: index out of range [0] with length 0
</pre></div> </div> </li> <li><p>If the ksqlDB REST endpoint is using the auto-generated certificates, the ksqlDB deployment that points to Confluent Cloud requires trusting the Let’s Encrypt CA.</p> <p>For this to work, you must provide a CA bundle through <code class="docutils literal notranslate"><span class="pre">cacerts.pem</span></code> that contains both (1) the Confluent Cloud CA and (2) the self-signed CA to the ksqlDB CR.</p> </li> <li><p>When TLS is enabled, and when Confluent Control Center (Legacy) uses a different TLS certificate to communicate with MDS or Confluent Cloud Schema Registry, Control Center (Legacy) (used with Confluent Platform 7.x) cannot use an auto-generated TLS certificate to connect to MDS or Confluent Cloud Schema Registry. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-troubleshooting.html#co-c3-mds-certificates"><span class="std std-ref">Troubleshooting Guide</span></a> for a workaround.</p></li> <li><p>When deploying the Schema Registry and Kafka CRs simultaneously, Schema Registry could fail because it cannot create topics with a replication factor of 3. It is because the Kafka brokers have not fully started.</p> <p>The workaround is to delete the Schema Registry deployment and re-deploy once Kafka is fully up.</p> </li> <li><p>When deploying an RBAC-enabled Kafka cluster in centralized mode, where another “secondary” Kafka is being used to store RBAC metadata, an error, “License Topic could not be created”, may return on the secondary Kafka cluster.</p></li> <li><p>A periodic Kubernetes TCP probe on ZooKeeper (in Confluent Platform 7.x) causes frequent warning messages “client has closed socket” when warning logs are enabled.</p></li> <li><p>REST Proxy configured with monitoring interceptors is missing the callback handler properties when RBAC is enabled. Interceptor would not work, and you would see an error message in the KafkaRestProxy log.</p> <p>As a workaround, manually add configuration overrides as shown in the following KafkaRestProxy CR:</p> <div class="highlight-yaml notranslate"><div class="highlight"><pre><span></span><span class="nt">configOverrides</span><span class="p">:</span>
<span class="w">  </span><span class="nt">server</span><span class="p">:</span>
<span class="w">    </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">confluent.monitoring.interceptor.sasl.login.callback.handler.class=io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler</span>
<span class="w">    </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">consumer.confluent.monitoring.interceptor.sasl.login.callback.handler.class=io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler</span>
<span class="w">    </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">producer.confluent.monitoring.interceptor.sasl.login.callback.handler.class=io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler</span>
</pre></div> </div> </li> <li><p>When configuring source-initiated cluster links with CFK where the source cluster has TLS enabled, set the following in the Source mode ClusterLink CR, under the <code class="docutils literal notranslate"><span class="pre">spec.configs</span></code> section:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">local.security.protocol:</span> <span class="pre">SSL</span></code> and <code class="docutils literal notranslate"><span class="pre">local.listener.name:</span> <span class="pre">&lt;SSL</span> <span class="pre">listener</span>
<span class="pre">name&gt;</span></code> for mTLS.</p></li> <li><p><code class="docutils literal notranslate"><span class="pre">local.security.protocol:</span> <span class="pre">SASL_SSL</span></code> for SASL authentication with TLS.</p></li> </ul> <p>For details about configuring source-initiated Cluster Linking, see <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-link-clusters.html#co-clusterlink-source-initiated-connection-source-mode"><span class="std std-ref">Configure the source-initiated cluster link on the source cluster</span></a>.</p> </li> <li><p>The CFK <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-troubleshooting.html#co-support-bundle"><span class="std std-ref">support bundle plugin</span></a> on Windows systems does not capture all the logs.</p> <p>As a workaround, specify the <code class="docutils literal notranslate"><span class="pre">--out-dir</span></code> flag in the <code class="docutils literal notranslate"><span class="pre">kubectl</span> <span class="pre">confluent</span>
<span class="pre">support-bundle</span></code> command to provide the output location for the support bundle.</p> </li> <li><p>When you have external access enabled with load balancer type for both Control Center and Prometheus, only <code class="docutils literal notranslate"><span class="pre">controlcenter-next-gen-prometheus-bootstrap-lb</span></code> gets created.</p> <p>The workaround is to enable Control Center external access first, and then add Prometheus external access. This will show both Control Center and Prometheus external <code class="docutils literal notranslate"><span class="pre">controlcenter-next-gen-bootstrap-lb</span></code> and <code class="docutils literal notranslate"><span class="pre">controlcenter-next-gen-prometheus-bootstrap-lb</span></code> get created.</p> </li> </ul> </section> <section id="known-gaps-from-cp-cp-version"> <h3>Known gaps from Confluent Platform 8.1<a class="headerlink" href="#known-gaps-from-cp-cp-version" title="Link to this heading"></a></h3> <p>CFK 3.1 does not support the following Confluent Platform 8.1 functionality:</p> <ul class="simple"> <li><p>Kafka authentication mechanisms: Kerberos and SASL/Scram</p></li> </ul> </section> ]]></description><content:encoded><![CDATA[ <p>CFK 3.1.0 allows you to deploy and manage Confluent Platform versions from 7.3.x to 8.1.x on Kubernetes versions 1.26 - 1.34 (OpenShift 4.13 -4.19).</p> <p>The images released in CFK 3.1.0 are:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-operator:0.1351.24</span></code></p></li> <li><p><code class="docutils literal notranslate"><span class="pre">confluentinc/confluent-init-container:3.1.0</span></code></p></li> </ul> <p>For details on installing CFK and Confluent Platform using the above images, see <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cfk.html#co-deploy-operator"><span class="std std-ref">Deploy Confluent for Kubernetes</span></a> and <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-deploy-cp.html#co-deploy-cp"><span class="std std-ref">Deploy Confluent Platform using Confluent for Kubernetes</span></a>.</p> <section id="new-features-and-enhancements"> <h3>New features and enhancements<a class="headerlink" href="#new-features-and-enhancements" title="Link to this heading"></a></h3> <p>CFK 3.1.0 is a minor release with the following noteworthy new features and updates.</p> <dl> <dt>Confluent Unified Stream Manager Agent Support</dt><dd><p>You can use CFK to deploy Unified Stream Manager.</p> <p>See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-configure-usm.html#co-usm"><span class="std std-ref">Configure, Deploy, and Manage Unified Stream Manager Using Confluent for Kubernetes</span></a>.</p> </dd> <dt>Unified Stream Manager Schema Registry Support</dt><dd><p>You can use CFK to deploy Unified Stream Manager Schema Registry.</p> <p>See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-schema-registry-switchover.html#co-schema-registry-switchover"><span class="std std-ref">Set up Schema Registry Switchover with Unified Stream Manager</span></a>.</p> </dd> <dt>Confluent Private Cloud Gateway Support</dt><dd><p>You can use CFK to deploy Confluent Gateway.</p> <p>See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/gateway/co-gateway-overview.html#co-gateway-overview"><span class="std std-ref">Deploy and Manage Confluent Gateway with Confluent for Kubernetes</span></a>.</p> </dd> <dt>Removal of Confluent for Kubernetes (CFK) Blueprints</dt><dd><p>Confluent for Kubernetes (CFK) Blueprints (the <a class="reference external" href="https://hub.docker.com/r/confluentinc/cpc-operator">cpc-operator</a> image) is deprecated and removed in this release. The image is still available on Docker Hub for existing deployments but is no longer updated or patched for security vulnerabilities.</p> </dd> </dl> </section> <section id="notable-update"> <h3>Notable update<a class="headerlink" href="#notable-update" title="Link to this heading"></a></h3> <p>A new Confluent Enterprise license is available for the customer-managed Confluent Platform for Confluent Cloud subscription. This license allows you to use self-managed Confluent Platform components exclusively with Confluent Cloud services.</p> <p>If you encounter the following error when provisioning a new license, you should upgrade to a CFK version, 2.9.7, 2.10.3, 2.11.3, 3.0.1, 3.1.0, or later.</p> <div class="highlight-text notranslate"><div class="highlight"><pre><span></span>secretRef confluent-license: missing subject or contains invalid subject
</pre></div> </div> </section> <section id="known-issues"> <h3>Known issues<a class="headerlink" href="#known-issues" title="Link to this heading"></a></h3> <ul> <li><p>When deploying CFK to Red Hat OpenShift with Red Hat’s Operator Lifecycle Manager using the OperatorHub, you must use OpenShift version 4.9 or higher.</p> <p>This OpenShift version restriction does not apply when deploying CFK to Red Hat OpenShift in the standard way without using the Red Hat Operator Lifecycle Manager.</p> </li> <li><p>When CFK is deployed on an OpenShift cluster with Red Hat’s Operator LIfecycle Manager/OperatorHub, capturing the support bundle for CFK using the command, <code class="docutils literal notranslate"><span class="pre">kubectl</span> <span class="pre">confluent</span> <span class="pre">support-bundle</span> <span class="pre">--namespace</span> <span class="pre">&lt;namespace&gt;</span></code>, can fail with the following error message:</p> <div class="highlight-text notranslate"><div class="highlight"><pre><span></span>panic: runtime error: index out of range [0] with length 0
</pre></div> </div> </li> <li><p>If the ksqlDB REST endpoint is using the auto-generated certificates, the ksqlDB deployment that points to Confluent Cloud requires trusting the Let’s Encrypt CA.</p> <p>For this to work, you must provide a CA bundle through <code class="docutils literal notranslate"><span class="pre">cacerts.pem</span></code> that contains both (1) the Confluent Cloud CA and (2) the self-signed CA to the ksqlDB CR.</p> </li> <li><p>When TLS is enabled, and when Confluent Control Center (Legacy) uses a different TLS certificate to communicate with MDS or Confluent Cloud Schema Registry, Control Center (Legacy) (used with Confluent Platform 7.x) cannot use an auto-generated TLS certificate to connect to MDS or Confluent Cloud Schema Registry. See <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-troubleshooting.html#co-c3-mds-certificates"><span class="std std-ref">Troubleshooting Guide</span></a> for a workaround.</p></li> <li><p>When deploying the Schema Registry and Kafka CRs simultaneously, Schema Registry could fail because it cannot create topics with a replication factor of 3. It is because the Kafka brokers have not fully started.</p> <p>The workaround is to delete the Schema Registry deployment and re-deploy once Kafka is fully up.</p> </li> <li><p>When deploying an RBAC-enabled Kafka cluster in centralized mode, where another “secondary” Kafka is being used to store RBAC metadata, an error, “License Topic could not be created”, may return on the secondary Kafka cluster.</p></li> <li><p>A periodic Kubernetes TCP probe on ZooKeeper (in Confluent Platform 7.x) causes frequent warning messages “client has closed socket” when warning logs are enabled.</p></li> <li><p>REST Proxy configured with monitoring interceptors is missing the callback handler properties when RBAC is enabled. Interceptor would not work, and you would see an error message in the KafkaRestProxy log.</p> <p>As a workaround, manually add configuration overrides as shown in the following KafkaRestProxy CR:</p> <div class="highlight-yaml notranslate"><div class="highlight"><pre><span></span><span class="nt">configOverrides</span><span class="p">:</span>
<span class="w">  </span><span class="nt">server</span><span class="p">:</span>
<span class="w">    </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">confluent.monitoring.interceptor.sasl.login.callback.handler.class=io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler</span>
<span class="w">    </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">consumer.confluent.monitoring.interceptor.sasl.login.callback.handler.class=io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler</span>
<span class="w">    </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">producer.confluent.monitoring.interceptor.sasl.login.callback.handler.class=io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler</span>
</pre></div> </div> </li> <li><p>When configuring source-initiated cluster links with CFK where the source cluster has TLS enabled, set the following in the Source mode ClusterLink CR, under the <code class="docutils literal notranslate"><span class="pre">spec.configs</span></code> section:</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">local.security.protocol:</span> <span class="pre">SSL</span></code> and <code class="docutils literal notranslate"><span class="pre">local.listener.name:</span> <span class="pre">&lt;SSL</span> <span class="pre">listener</span>
<span class="pre">name&gt;</span></code> for mTLS.</p></li> <li><p><code class="docutils literal notranslate"><span class="pre">local.security.protocol:</span> <span class="pre">SASL_SSL</span></code> for SASL authentication with TLS.</p></li> </ul> <p>For details about configuring source-initiated Cluster Linking, see <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-link-clusters.html#co-clusterlink-source-initiated-connection-source-mode"><span class="std std-ref">Configure the source-initiated cluster link on the source cluster</span></a>.</p> </li> <li><p>The CFK <a class="reference internal" href="https://docs.confluent.io/operator/3.1/co-troubleshooting.html#co-support-bundle"><span class="std std-ref">support bundle plugin</span></a> on Windows systems does not capture all the logs.</p> <p>As a workaround, specify the <code class="docutils literal notranslate"><span class="pre">--out-dir</span></code> flag in the <code class="docutils literal notranslate"><span class="pre">kubectl</span> <span class="pre">confluent</span>
<span class="pre">support-bundle</span></code> command to provide the output location for the support bundle.</p> </li> <li><p>When you have external access enabled with load balancer type for both Control Center and Prometheus, only <code class="docutils literal notranslate"><span class="pre">controlcenter-next-gen-prometheus-bootstrap-lb</span></code> gets created.</p> <p>The workaround is to enable Control Center external access first, and then add Prometheus external access. This will show both Control Center and Prometheus external <code class="docutils literal notranslate"><span class="pre">controlcenter-next-gen-bootstrap-lb</span></code> and <code class="docutils literal notranslate"><span class="pre">controlcenter-next-gen-prometheus-bootstrap-lb</span></code> get created.</p> </li> </ul> </section> <section id="known-gaps-from-cp-cp-version"> <h3>Known gaps from Confluent Platform 8.1<a class="headerlink" href="#known-gaps-from-cp-cp-version" title="Link to this heading"></a></h3> <p>CFK 3.1 does not support the following Confluent Platform 8.1 functionality:</p> <ul class="simple"> <li><p>Kafka authentication mechanisms: Kerberos and SASL/Scram</p></li> </ul> </section> ]]></content:encoded></item></channel></rss>