KafkaCluster CR Examples

The following KafkaCluster custom resource examples show you some basic use cases. You can use these examples as a base for your own Kafka cluster.

KafkaCluster CR with detailed explanation

This is our most descriptive KafkaCluster CR. You can find a lot of valuable explanation about the settings.

• Detailed CR with descriptions

Kafka cluster with monitoring

This is a very simple KafkaCluster CR with Prometheus monitoring enabled.

• Simple KafkaCluster with monitoring

Kafka cluster with ACL, SSL, and rack awareness

You can read more details about rack awareness here.

• Use SSL and rack awareness

Kafka cluster with broker configuration

• Use broker configuration groups
• Use independent broker configurations

Kafka cluster with custom SSL certificates for external listeners

You can specify custom SSL certificates for listeners.
For details about SSL configuration, see Securing Kafka With SSL.

• Use custom SSL certificate for an external listener
• Use custom SSL certificate for controller and inter-broker communication. In this case you also need to provide the client SSL certificate for Koperator.
• Hybrid solution: some listeners have custom SSL certificates and some use certificates Koperator has generated automatically using cert-manager.

Kafka cluster with SASL

You can use SASL authentication on the listeners. For details, see Expose the Kafka cluster to external applications.

• Use SASL authentication on the listeners

Kafka cluster with load balancers and brokers in the same availability zone

You can create a broker-ingress mapping to eliminate traffic across availability zones between load balancers and brokers by configuring load balancers for brokers in same availability zone.

• Load balancers and brokers in same availability zone

Kafka cluster with Istio

You can use Istio as the ingress controller for your external listeners. It requires using our Istio operator in the Kubernetes cluster.

• Kafka cluster with Istio as ingress controller

Kafka cluster with custom advertised address for external listeners and brokers

You can set custom advertised IP address for brokers.
This is useful when you’re advertising the brokers on an IP address different from the Kubernetes node IP address.
You can also set custom advertised address for external listeners.
For details, see Expose the Kafka cluster to external applications.

• Custom advertised address for external listeners

Kafka cluster with Kubernetes scheduler affinity settings

You can set node affinity for your brokers.

• Custom affinity settings

Kafka cluster with custom storage class

You can configure your brokers to use custom storage classes.

• Custom storage class