You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A StatefulSetboiling-heron-cp-kafka which contains 3 Kafka Pods: boiling-heron-cp-kafka-<0|1|2>. Each Pod has a container running a Kafka Broker and an optional sidecar JMX Exporter Container.
A Serviceboiling-heron-cp-kafka for clients to connect to Kafka.
A Headless Serviceboiling-heron-cp-kafka-headless to control the network domain for the Kafka processes.
A group(N = number of brokers) of NodePort Serviceboiling-heron-cp-kafka-${i}-external to allow access to Kafka Cluster from outside.
A ConfigMap which contains configuration for Prometheus JMX Exporter.
Configuration
You can specify each parameter using the --set key=value[,key=value] argument to helm install.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
Whether or not to allow access to kafka cluster from outside k8s through NodePort.
false
nodeport.servicePort
The Port broker will advertise to external producers and consumers.
19092
nodeport.firstListenerPort
The first NodePort that Kafka Broker will use for advertising to external producers and consumers. For each broker, advertise.listeners port for external will be set to 31090 + {index of broker pod}.
31090
Deployment Topology
Parameter
Description
Default
nodeSelector
Dictionary containing key-value-pairs to match labels on nodes. When defined pods will only be scheduled on nodes, that have each of the indicated key-value pairs as labels. Further information can be found in the Kubernetes documentation
{}
tolerations
Array containing taint references. When defined, pods can run on nodes, which would otherwise deny scheduling. Further information can be found in the Kubernetes documentation
{}
Dependencies
Zookeeper
Parameter
Description
Default
cp-zookeeper.enabled
Whether or not to install cp-zookeeper chart alongside cp-kafka chart
true
cp-zookeeper.persistence.enabled
Whether to create a PVC. If false, an emptyDir on the host will be used.
true
cp-zookeeper.persistence.dataDirSize
Size for Data dir, where ZooKeeper will store the in-memory database snapshots. This will overwrite corresponding value in cp-zookeeper chart's value.yaml
5Gi
cp-zookeeper.persistence.dataLogDirSize
Size for data log dir, which is a dedicated log device to be used, and helps avoid competition between logging and snapshots. This will overwrite corresponding value in cp-zookeeper chart's value.yaml.
5Gi
cp-zookeeper.url
Service name of Zookeeper cluster (Not needed if zookeeper.enabled is set to true).