About Confluent Operator¶
Confluent Operator allows you to deploy and manage Confluent Platform as a cloud-native, stateful container application on Kubernetes and OpenShift. The automation provided by Kubernetes, Operator, and Helm greatly simplifies provisioning and minimizes the burden of operating and managing Confluent Platform clusters. Operator also provides you with the portability to use Apache Kafka® in multiple provider zones and across both your private and public cloud environments.
- Automates Confluent Platform deployment using Helm.
- Automates Confluent Platform management.
- Uses default Kubernetes StorageClass-based provisioners for persistent volume storage (such as Google persistent disks, AWS EBS, and Azure disk storage).
- Automates cluster authentication and security configuration using:
- SASL/PLAIN with TLS certificates
- TLS two-way (mutual) authentication
- TLS in-transit encryption for all deployed components.
- Updating and upgrading
- Provides automated rolling updates for configuration changes.
- Provides automated rolling upgrades with no impact to Kafka availability.
- Provides elastic scaling for new Confluent Platform components (with manual rebalancing).
- Restores a Kafka pod with the same Kafka broker ID, configuration, and persistent storage volumes if a failure occurs.
- Supports metrics aggregation using JMX/Jolokia.
- Supports aggregated metrics export to Prometheus.
Operator 1.3.0 is released with Confluent Platform 5.3. For the compatibility information with any other versions of Confluent Platform, see Kubernetes.
Confluent Operator automates the deployment and management of Confluent Platform in the following environments:
- Amazon Elastic Kubernetes Service (EKS) cluster running on Amazon Web Services (AWS)
- Azure Kubernetes Service (AKS) cluster running on Microsoft Azure (Azure)
- Google Kubernetes Engine (GKE) cluster running on Google Cloud Platform (GCP)
- OpenShift (3.9 or later) cluster running in a datacenter private cloud
- Pivotal Container Service (PKS) cluster running in a datacenter private cloud
- Vanilla Kubernetes (1.9 or later) cluster
The following shows the high-level architecture of Operator and Confluent Platform components in a Kubernetes cluster.
You can use Confluent Operator for a 30-day trial period without a license key.
After 30 days, Operator requires a license key. Confluent issues keys to subscribers, along with providing enterprise-level support for Confluent Platform and Confluent Operator. If you are a subscriber, please contact Confluent Support at email@example.com for more information.
See Adding a license key if you have received a key for Confluent Operator.
Refer to the following sections for detailed information about Confluent Operator and how to deploy Operator and Confluent Platform in a Kubernetes or OpenShift cluster.
To get started with Confluent Operator on Kubernetes, try out the Kubernetes Demos.
You should have experience using Linux and experience configuring Kubernetes or OpenShift before using these instructions. Detailed information about installing and configuring Kubernetes and OpenShift is not provided.