Confluent Platform Self-Managed
Self-managed event streaming platform deployed to customer-operated Kubernetes with Confluent for Kubernetes.
9 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Confluent Platform November security patches
Vendor advisories cover broker/Connect, CA trust, JWT, ZooKeeper and denial-of-service issues; component conditions vary.
Scope: Confluent Platform fixes: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3 or 8.4.1, as applicable to each advisory. CFK/operator versions are separate.
Kafka Connect admin.listeners creates a separate affected administrative surface. ZooKeeper fixes apply only to the vendor-identified 7.x lines; do not transfer these claims to Confluent Cloud.
Action: Use each advisory to choose the patched branch and compatible CFK/components. Until patched, remove the separate Connect admin.listeners setting.
Primary source · Compromised CA trust remediation · Connect administrative listener mitigation · Reviewed 2026-11-17
Confluent CONFSA-2026-37 Java4Shell guidance
CONFSA-2026-37 covers CVE-2026-114938 in customer-JDK installs and multiple Confluent Docker-image ranges.
Scope: Confluent Platform 7.6.x–8.4.x, Control Center 2.0.x–2.7.x and the exact additional image ranges in the advisory.
Package/archive installs inherit the customer JDK; Docker applicability depends on the image and tag.
Action: Apply -XX:-UseBASE64Intrinsics, restart and verify every affected Java process until a fixed vendor image or JDK is deployed.
Primary source · Reviewed 2026-11-19
What lands where
Supplied by
Vendor or project
Install the Confluent for Kubernetes operator with Helm, then deploy Confluent Platform components through Kubernetes custom resources.
Runs in
Documented customer environment
CFK operator managing persistent Kafka, KRaft, Schema Registry, Connect, ksqlDB and other selected Confluent Platform services in a customer Kubernetes cluster
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer manages Kubernetes clusters, node pools, persistent storage, load balancers, DNS and routing, identity and RBAC, secrets, backups, scaling and upgrades; CFK reconciles the declared Confluent application resources.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Confluent for Kubernetes guidance for EKS, AKS and GKE ↗ · Source checked 2026-11-16
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Confluent for Kubernetes guidance for EKS, AKS and GKE ↗ · Source checked 2026-11-16
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Confluent for Kubernetes guidance for EKS, AKS and GKE ↗ · Source checked 2026-11-16
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Install the Confluent for Kubernetes operator with Helm, then deploy Confluent Platform components through Kubernetes custom resources. |
|---|---|
| Infrastructure | Servers / containers CFK deploys long-running stateful brokers, controllers and supporting services on customer Kubernetes worker nodes with persistent storage. Using a managed Kubernetes control plane does not make the Confluent Platform application runtime serverless. |
| Licensing model | Commercial Only This entry specifically covers deployment through Confluent for Kubernetes. Confluent states that deploying with CFK requires a subscription and applies licensing requirements to every Confluent Platform component in that cluster. Some components can use Apache 2.0 or Confluent Community licenses outside this CFK path, but that does not make the selected CFK deployment an open-source offering. |
| License | A commercial Confluent subscription is required for Confluent Platform components deployed with CFK; component licenses otherwise vary. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
8 of 12 fields researched (67%) · 6 documented · 2 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
Control Center supports OIDC SSO and automated configuration through CFK. The guide says IdP refresh-token rotation must be disabled for this integration. This is self-managed Control Center authentication, distinct from Confluent Cloud SAML.
Confluent Platform Control Center OIDC; requires the relevant licensed components · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Compliance attestations
Not confirmedEvidence and scope for Compliance attestations
The Platform guide says Confluent’s annual SOC 2 report is available on request. It does not supply the current report period or customer-environment scope; its separate FIPS configuration guidance must not be treated as a whole-deployment attestation.
Vendor security-controls report availability and deployment configuration; actual attestation scope unresolved · Source ↗ · Reviewed 2026-11-16
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
CFK telemetry is disabled by default; enabling Health+ sends service metadata to Confluent. The built-in JMX Prometheus exporter lacks authentication/encryption and cannot be disabled through CFK, so restrict access at the network boundary and configure other security surfaces separately. Current review: CONFSA-2026-37 covers CVE-2026-114938 in package/archive installs using affected customer JDKs and in the advisory's Platform, Control Center, CMF, Flink, operator, Gateway and CFK init-container image ranges. Fixed-runtime releases were still in preparation. Apply -XX:-UseBASE64Intrinsics, restart and verify every affected Java process until a fixed vendor image or JDK is deployed.
Confluent Platform 7.6.x–8.4.x, Control Center 2.0.x–2.7.x and the exact Docker-image ranges in CONFSA-2026-37 · Source ↗ · Prior security-controls source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation
CFK documents copying the required tagged Platform/operator/init-container images into a private registry and configuring pulls from it. This establishes private image delivery, but the reviewed guide does not establish end-to-end offline licensing, dependencies or updates for the selected stack.
CFK private-registry installation mechanics; full disconnected operation remains unresolved · Source ↗ · Reviewed 2026-11-16
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The CFK guide installs confluent-for-kubernetes from Confluent’s Helm repository, then manages Platform components through custom resources. The repository index moves; select a CFK/chart release compatible with the Platform components and Kubernetes version.
Confluent for Kubernetes deployment; commercial subscription applies · Source ↗ · Deployment artifact ↗ (moving Helm repository index; select compatible chart version) · Reviewed 2026-11-16
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The current CFK guide starts with three Kafka brokers and three KRaft controllers. Each broker’s minimum is 4 CPUs, 16 GB RAM and 1 TB disk; the production column is larger. Controllers and other components add resources.
CFK minimum cluster planning; not aggregate production sizing or pre-8.0 ZooKeeper guidance · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
This entry specifically covers deployment through Confluent for Kubernetes. Confluent states that deploying with CFK requires a subscription and applies licensing requirements to every Confluent Platform component in that cluster. Some components can use Apache 2.0 or Confluent Community licenses outside this CFK path, but that does not make the selected CFK deployment an open-source offering.
Confluent Platform Self-Managed: software license terms; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The reviewed compatibility matrix dates CFK 3.4.x to 2026-10-28, with standard support through 2028-10-28. It supports Platform 7.6.x–8.4.x and lists separate Control Center and Kubernetes ranges. The operator, init container and Platform have distinct versions; do not use a Platform patch number as the chart/operator version.
CFK 3.4 release-line/support and component compatibility; not a claim about the newest Platform patch · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
Show all fields (4 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
This entry covers self-managed Confluent Platform deployed with Confluent for Kubernetes, not Confluent Cloud. Current CFK guidance explicitly addresses Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. Provider examples do not certify every Kubernetes, Confluent Platform or topology combination; use the current supported-environments matrix and validate cross-cluster networking, storage, security, version compatibility and subscription terms. Confluent's November 2026 security releases address multiple broker, Kafka Connect, ZooKeeper, TLS trust, JWT, file-read, and denial-of-service issues. Upgrade to the latest patched release for the deployed branch: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3, or 8.4.1. Until patched, deployments using a separate Kafka Connect administrative listener should remove admin.listeners; the ZooKeeper fix applies to the affected 7.x lines identified by Confluent. CONFSA-2026-37 covers CVE-2026-114938 in Confluent Platform 7.6.x–8.4.x and Control Center 2.0.x–2.7.x when package/archive installs use affected customer JDKs, plus specified Docker-image ranges. Fixed-runtime releases were still being prepared at review time. Apply -XX:-UseBASE64Intrinsics to every affected Java process, restart and verify the flag until the applicable fixed image or runtime is available.
Category fit
- Streaming
- Runs Apache Kafka brokers together with schema, connector and stream-processing services for customer-operated event streaming.
Compare within Streaming
- Aiven for Apache Kafka BYOCManaged Apache Kafka brokers in the customer's cloud account, operated by Aiven.
- AWS
- Azure
- Google Cloud
- Apache KafkaDistributed event streaming platform for durable publication, storage and consumption of event streams.
- Google Cloud
- Apache PulsarDistributed publish-subscribe messaging and streaming platform for persistent event workloads.
- AWS
- Cloudera on CloudCloudera-managed control plane that provisions data, analytics and AI workload services into a customer's public-cloud account.
- AWS
- Azure
- Google Cloud
- Redpanda BYOCManaged Kafka-compatible streaming in your cloud account.
- AWS
- Azure
- Google Cloud
These products address related workflows; read their category-fit notes before comparing scope. See all of Streaming →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Confluent for Kubernetes overview ↗docs.confluent.io
- Deploy Confluent for Kubernetes ↗docs.confluent.io
- Supported environments and versions ↗docs.confluent.io
- CFK multi-region deployment guidance ↗docs.confluent.io
- Confluent Platform licensing ↗docs.confluent.io
- Confluent November 2026 security advisories and patched releases ↗support.confluent.io
- Confluent compromised CA trust advisory ↗support.confluent.io
- Confluent Kafka Connect administrative-listener advisory ↗support.confluent.io
- CONFSA-2026-37 Java4Shell advisory ↗support.confluent.io
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Confluent for Kubernetes guidance for EKS, AKS and GKE ↗ · AWS, Azure, Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
The current CFK multi-region guide explicitly identifies Google Kubernetes Engine, Amazon Elastic Kubernetes Service and Azure Kubernetes Service for provider-specific configuration and validation. The CFK overview defines the product as managing self-managed Confluent Platform in the customer's own Kubernetes environment. This evidence does not include the separately operated Confluent Cloud service.
- Confluent for Kubernetes guidance for EKS, AKS and GKE ↗ · AWS, Azure, Google Cloud
- Infrastructure evidenceChecked
- Licensing evidenceChecked