The operator installs version 3.1.0 of Apache Kafka, and can run on:

  • Minikube v0.33.1+,
  • Kubernetes 1.21-1.24, and
  • Red Hat OpenShift 4.10-4.11.

The operator supports Kafka 2.6.2-3.1.x.

CAUTION:

The ZooKeeper and the Kafka clusters need persistent volume (PV) to store data. Therefore, when installing the operator on Amazon EKS with Kubernetes version 1.23 or later, you must install the EBS CSI driver add-on on your cluster.

Prerequisites 🔗︎

  • A Kubernetes cluster (minimum 6 vCPU and 10 GB RAM). Red Hat OpenShift is also supported in Koperator version 0.24 and newer, but note that it needs some permissions for certain components to function.

We believe in the separation of concerns principle, thus the Koperator does not install nor manage Apache ZooKeeper or cert-manager. If you would like to have a fully automated and managed experience of Apache Kafka on Kubernetes, try Cisco Streaming Data Manager.

Install Koperator and all requirements using Supertubes

This method uses a command-line tool of the commercial Banzai Cloud Supertubes product to install the Koperator and its prerequisites. If you’d prefer to install these components manually, see Install Koperator and the requirements independently.

  1. Register for an evaluation version of Supertubes.

  2. Install the Supertubes CLI tool for your environment by running the following command:

    Evaluation downloads are temporarily suspended. Contact us to discuss your needs and requirements, and organize a live demo.

  3. Run the following command:

    supertubes install -a

Install Koperator and its requirements independently

Install cert-manager with Helm 🔗︎

Koperator uses cert-manager for issuing certificates to clients and brokers and cert-manager is required for TLS-encrypted client connections. It is recommended to deploy and configure a cert-manager instance if there is none in your environment yet.

Note:

  • Koperator 0.24.0 and newer versions support cert-manager 1.10.0+ (which is a requirement for Red Hat OpenShift)
  • Koperator 0.18.1 and newer supports cert-manager 1.5.3-1.9.x
  • Koperator 0.8.x-0.17.0 supports cert-manager 1.3.x

  1. Install cert-manager’s CustomResourceDefinitions.

    kubectl apply \
--validate=false \
-f https://github.com/jetstack/cert-manager/releases/download/v1.11.0/cert-manager.crds.yaml

    Expected output:

    customresourcedefinition.apiextensions.k8s.io/certificaterequests.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/certificates.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/challenges.acme.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/clusterissuers.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/issuers.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/orders.acme.cert-manager.io created

  2. If you are installing cert-manager on a Red Hat OpenShift version 4.10 cluster, the default security computing profile must be enabled for cert-manager to work.

    1. Create a new SecurityContextConstraint object named restricted-seccomp which will be a copy of the OpenShift built-in restricted SecurityContextConstraint, but will also allow the runtime/default / RuntimeDefault security computing profile according to the OpenShift documentation.

      oc create -f - <<EOF
allowHostDirVolumePlugin: false
allowHostIPC: false
allowHostNetwork: false
allowHostPID: false
allowHostPorts: false
allowPrivilegeEscalation: true
allowPrivilegedContainer: false
allowedCapabilities: null
apiVersion: security.openshift.io/v1
defaultAddCapabilities: null
fsGroup:
    type: MustRunAs
groups:
    - system:authenticated
kind: SecurityContextConstraints
metadata:
    annotations:
        include.release.openshift.io/ibm-cloud-managed: "true"
        include.release.openshift.io/self-managed-high-availability: "true"
        include.release.openshift.io/single-node-developer: "true"
        kubernetes.io/description: restricted denies access to all host features and requires pods to be run with a UID, and SELinux context that are allocated to the namespace.  This is the most restrictive SCC and it is used by default for authenticated users.
        release.openshift.io/create-only: "true"
    name: restricted-seccomp # ~
priority: null
readOnlyRootFilesystem: false
requiredDropCapabilities:
    - KILL
    - MKNOD
    - SETUID
    - SETGID
runAsUser:
    type: MustRunAsRange
seLinuxContext:
    type: MustRunAs
seccompProfiles: # +
    - runtime/default # +
supplementalGroups:
    type: RunAsAny
users: []
volumes:
    - configMap
    - downwardAPI
    - emptyDir
    - persistentVolumeClaim
    - projected
    - secret
EOF

      Expected output:

      securitycontextconstraints.security.openshift.io/restricted-seccomp created

    2. Elevate the permissions of the namespace containing the cert-manager service account.

      • Using the default cert-manager namespace:

        oc adm policy add-scc-to-group restricted-seccomp system:serviceaccounts:cert-manager

      • Using a custom namespace for cert-manager:

        oc adm policy add-scc-to-group anyuid system:serviceaccounts:{NAMESPACE_FOR_CERT_MANAGER_SERVICE_ACCOUNT}

      Expected output:

      clusterrole.rbac.authorization.k8s.io/system:openshift:scc:restricted-seccomp added: "system:serviceaccounts:{NAMESPACE_FOR_CERT_MANAGER_SERVICE_ACCOUNT}"

  3. Install cert-manager.

    helm install \
cert-manager \
--repo https://charts.jetstack.io cert-manager \
--version v1.11.0 \
--namespace cert-manager \
--create-namespace \
--atomic \
--debug

    Expected output:

    install.go:194: [debug] Original chart version: "v1.11.0"
install.go:211: [debug] CHART PATH: /Users/pregnor/.cache/helm/repository/cert-manager-v1.11.0.tgz

# ...
NAME: cert-manager
LAST DEPLOYED: Thu Mar 23 08:40:07 2023
NAMESPACE: cert-manager
STATUS: deployed
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
{}

COMPUTED VALUES:
# ...
NOTES:
cert-manager v1.11.0 has been deployed successfully!

In order to begin issuing certificates, you will need to set up a ClusterIssuer
or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer).

More information on the different types of issuers and how to configure them
can be found in our documentation:

https://cert-manager.io/docs/configuration/

For information on how to configure cert-manager to automatically provision
Certificates for Ingress resources, take a look at the `ingress-shim`
documentation:

https://cert-manager.io/docs/usage/ingress/

  4. Verify that cert-manager has been deployed and is in running state.

    kubectl get pods -n cert-manager

    Expected output:

    NAME                                      READY   STATUS    RESTARTS   AGE
cert-manager-6b4d84674-4pkh4               1/1     Running   0          117s
cert-manager-cainjector-59f8d9f696-wpqph   1/1     Running   0          117s
cert-manager-webhook-56889bfc96-x8szj      1/1     Running   0          117s

Install zookeeper-operator with Helm 🔗︎

Koperator requires Apache Zookeeper for Kafka operations. You must:

  • Deploy zookeeper-operator if your environment doesn’t have an instance of it yet.
  • Create a Zookeeper cluster if there is none in your environment yet for your Kafka cluster.

Note: You are recommended to create a separate ZooKeeper deployment for each Kafka cluster. If you want to share the same ZooKeeper cluster across multiple Kafka cluster instances, use a unique zk path in the KafkaCluster CR to avoid conflicts (even with previous defunct KafkaCluster instances).

  1. If you are installing zookeeper-operator on a Red Hat OpenShift cluster, elevate the permissions of the namespace containing the Zookeeper service account.

    • Using the default zookeeper namespace:

      oc adm policy add-scc-to-group anyuid system:serviceaccounts:zookeeper

    • Using a custom namespace for Zookeeper:

      oc adm policy add-scc-to-group anyuid system:serviceaccounts:{NAMESPACE_FOR_ZOOKEEPER_SERVICE_ACCOUNT}

    Expected output:

    clusterrole.rbac.authorization.k8s.io/system:openshift:scc:anyuid added: "system:serviceaccounts:{NAMESPACE_FOR_ZOOKEEPER_SERVICE_ACCOUNT}"

  2. Install ZooKeeper using the Pravega’s Zookeeper Operator.

    helm install \
zookeeper-operator \
--repo https://charts.pravega.io zookeeper-operator \
--version 0.2.14 \
--namespace=zookeeper \
--create-namespace \
--atomic \
--debug

    Expected output:

    install.go:194: [debug] Original chart version: "0.2.14"
install.go:211: [debug] CHART PATH: /Users/pregnor/.cache/helm/repository/zookeeper-operator-0.2.14.tgz

# ...
NAME: zookeeper-operator
LAST DEPLOYED: Thu Mar 23 08:42:42 2023
NAMESPACE: zookeeper
STATUS: deployed
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
{}

COMPUTED VALUES:
# ...

  3. Verify that zookeeper-operator has been deployed and is in running state.

    kubectl get pods --namespace zookeeper

    Expected output:

    NAME                                  READY   STATUS    RESTARTS   AGE
zookeeper-operator-5857967dcc-gm5l5   1/1     Running   0          3m22s

Deploy a Zookeeper cluster for Kafka 🔗︎

  1. Create a Zookeeper cluster.

    kubectl create -f - <<EOF
apiVersion: zookeeper.pravega.io/v1beta1
kind: ZookeeperCluster
metadata:
    name: zookeeper
    namespace: zookeeper
spec:
    replicas: 3
    persistence:
        reclaimPolicy: Delete
EOF

  2. Verify that Zookeeper has been deployed and is in running state with the configured number of replicas.

    kubectl get pods -n zookeeper

    Expected output:

    NAME                                  READY   STATUS    RESTARTS   AGE
zookeeper-0                           1/1     Running   0          27m
zookeeper-operator-54444dbd9d-2tccj   1/1     Running   0          28m

Install prometheus-operator with Helm 🔗︎

Koperator uses Prometheus for exporting metrics of the Kafka cluster. It is recommended to deploy a Prometheus instance if you don’t already have one.

  1. If you are installing prometheus-operator on a Red Hat OpenShift version 4.10 cluster, create a SecurityContextConstraints object nonroot-v2 with the following configuration for Prometheus admission and operator service accounts to work.

    oc create -f - <<EOF
allowHostDirVolumePlugin: false
allowHostIPC: false
allowHostNetwork: false
allowHostPID: false
allowHostPorts: false
allowPrivilegeEscalation: false
allowPrivilegedContainer: false
allowedCapabilities:
    - NET_BIND_SERVICE
apiVersion: security.openshift.io/v1
defaultAddCapabilities: null
fsGroup:
    type: RunAsAny
groups: []
kind: SecurityContextConstraints
metadata:
    annotations:
        include.release.openshift.io/ibm-cloud-managed: "true"
        include.release.openshift.io/self-managed-high-availability: "true"
        include.release.openshift.io/single-node-developer: "true"
        kubernetes.io/description: nonroot provides all features of the restricted SCC but allows users to run with any non-root UID.  The user must specify the UID or it must be specified on the by the manifest of the container runtime. On top of the legacy 'nonroot' SCC, it also requires to drop ALL capabilities and does not allow privilege escalation binaries. It will also default the seccomp profile to runtime/default if unset, otherwise this seccomp profile is required.
    name: nonroot-v2
priority: null
readOnlyRootFilesystem: false
requiredDropCapabilities:
    - ALL
runAsUser:
    type: MustRunAsNonRoot
seLinuxContext:
    type: MustRunAs
seccompProfiles:
    - runtime/default
supplementalGroups:
    type: RunAsAny
users: []
volumes:
    - configMap
    - downwardAPI
    - emptyDir
    - persistentVolumeClaim
    - projected
    - secret
EOF

    Expected output:

    securitycontextconstraints.security.openshift.io/nonroot-v2 created

  2. If you are installing prometheus-operator on a Red Hat OpenShift cluster, elevate the permissions of the Prometheus service accounts.

    Note: OpenShift doesn’t let you install Prometheus in the default namespace due to security considerations.

    • Using the default prometheus namespace:

      oc adm policy add-scc-to-user nonroot-v2 system:serviceaccount:prometheus:prometheus-kube-prometheus-admission
oc adm policy add-scc-to-user nonroot-v2 system:serviceaccount:prometheus:prometheus-kube-prometheus-operator
oc adm policy add-scc-to-user hostnetwork system:serviceaccount:prometheus:prometheus-operator-prometheus-node-exporter
oc adm policy add-scc-to-user node-exporter system:serviceaccount:prometheus:prometheus-operator-prometheus-node-exporter

    • Using a custom namespace or service account name for Prometheus:

      oc adm policy add-scc-to-user nonroot-v2 system:serviceaccount:{NAMESPACE_FOR_PROMETHEUS}:{PROMETHEUS_ADMISSION_SERVICE_ACCOUNT_NAME}
oc adm policy add-scc-to-user nonroot-v2 system:serviceaccount:{NAMESPACE_FOR_PROMETHEUS}:{PROMETHEUS_OPERATOR_SERVICE_ACCOUNT_NAME}
oc adm policy add-scc-to-user hostnetwork system:serviceaccount:{NAMESPACE_FOR_PROMETHEUS}:{PROMETHEUS_NODE_EXPORTER_SERVICE_ACCOUNT_NAME}
oc adm policy add-scc-to-user node-exporter system:serviceaccount:{NAMESPACE_FOR_PROMETHEUS}:{PROMETHEUS_NODE_EXPORTER_SERVICE_ACCOUNT_NAME}

    Expected output:

    clusterrole.rbac.authorization.k8s.io/system:openshift:scc:nonroot-v2 added: "{PROMETHEUS_ADMISSION_SERVICE_ACCOUNT_NAME}"
clusterrole.rbac.authorization.k8s.io/system:openshift:scc:nonroot-v2 added: "{PROMETHEUS_OPERATOR_SERVICE_ACCOUNT_NAME}"
clusterrole.rbac.authorization.k8s.io/system:openshift:scc:hostnetwork added: "{PROMETHEUS_NODE_EXPORTER_SERVICE_ACCOUNT_NAME}"
clusterrole.rbac.authorization.k8s.io/system:openshift:scc:node-exporter added: "{PROMETHEUS_NODE_EXPORTER_SERVICE_ACCOUNT_NAME}"

  3. Install the Prometheus operator and its CustomResourceDefinitions into the prometheus namespace.

    • On an OpenShift cluster:

      helm install \
prometheus \
--repo https://prometheus-community.github.io/helm-charts kube-prometheus-stack \
--version 42.0.1 \
--namespace prometheus \
--create-namespace \
--atomic \
--debug \
--set prometheusOperator.createCustomResource=true \
--set defaultRules.enabled=false \
--set alertmanager.enabled=false \
--set grafana.enabled=false \
--set kubeApiServer.enabled=false \
--set kubelet.enabled=false \
--set kubeControllerManager.enabled=false \
--set coreDNS.enabled=false \
--set kubeEtcd.enabled=false \
--set kubeScheduler.enabled=false \
--set kubeProxy.enabled=false \
--set kubeStateMetrics.enabled=false \
--set nodeExporter.enabled=false \
--set prometheus.enabled=false \
--set prometheusOperator.containerSecurityContext.capabilities.drop\[0\]="ALL" \
--set prometheusOperator.containerSecurityContext.seccompProfile.type=RuntimeDefault \
--set prometheusOperator.admissionWebhooks.createSecretJob.securityContext.allowPrivilegeEscalation=false \
--set prometheusOperator.admissionWebhooks.createSecretJob.securityContext.capabilities.drop\[0\]="ALL" \
--set prometheusOperator.admissionWebhooks.createSecretJob.securityContext.seccompProfile.type=RuntimeDefault \
--set prometheusOperator.admissionWebhooks.patchWebhookJob.securityContext.allowPrivilegeEscalation=false \
--set prometheusOperator.admissionWebhooks.patchWebhookJob.securityContext.capabilities.drop\[0\]="ALL" \
--set prometheusOperator.admissionWebhooks.patchWebhookJob.securityContext.seccompProfile.type=RuntimeDefault

    • On a regular Kubernetes cluster:

      helm install prometheus \
--repo https://prometheus-community.github.io/helm-charts kube-prometheus-stack \
--version 42.0.1 \
--namespace prometheus \
--create-namespace \
--atomic \
--debug \
--set prometheusOperator.createCustomResource=true \
--set defaultRules.enabled=false \
--set alertmanager.enabled=false \
--set grafana.enabled=false \
--set kubeApiServer.enabled=false \
--set kubelet.enabled=false \
--set kubeControllerManager.enabled=false \
--set coreDNS.enabled=false \
--set kubeEtcd.enabled=false \
--set kubeScheduler.enabled=false \
--set kubeProxy.enabled=false \
--set kubeStateMetrics.enabled=false \
--set nodeExporter.enabled=false \
--set prometheus.enabled=false

    Expected output:

    install.go:194: [debug] Original chart version: "45.7.1"
install.go:211: [debug] CHART PATH: /Users/pregnor/.cache/helm/repository/kube-prometheus-stack-45.7.1.tgz

# ...
NAME: prometheus
LAST DEPLOYED: Thu Mar 23 09:28:29 2023
NAMESPACE: prometheus
STATUS: deployed
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
# ...

COMPUTED VALUES:
# ...
NOTES:
kube-prometheus-stack has been installed. Check its status by running:
    kubectl --namespace prometheus get pods -l "release=prometheus"

Visit https://github.com/prometheus-operator/kube-prometheus for instructions on how to create & configure Alertmanager and Prometheus instances using the Operator.

  4. Verify that prometheus-operator has been deployed and is in running state.

    kubectl get pods -n prometheus

    Expected output:

    NAME                                                   READY   STATUS    RESTARTS   AGE
prometheus-kube-prometheus-operator-646d5fd7d5-s72jn   1/1     Running   0          15m

Install Koperator with Helm

Koperator can be deployed using its Helm chart.

  1. Install the Koperator CustomResourceDefinition resources (adjust the version number to the Koperator release you want to install). This is performed in a separate step to allow you to uninstall and reinstall Koperator without deleting your installed custom resources.

    kubectl create \
--validate=false \
-f https://github.com/banzaicloud/koperator/releases/download/v0.24.1/kafka-operator.crds.yaml

    Expected output:

    customresourcedefinition.apiextensions.k8s.io/cruisecontroloperations.kafka.banzaicloud.io created
customresourcedefinition.apiextensions.k8s.io/kafkaclusters.kafka.banzaicloud.io created
customresourcedefinition.apiextensions.k8s.io/kafkatopics.kafka.banzaicloud.io created
customresourcedefinition.apiextensions.k8s.io/kafkausers.kafka.banzaicloud.io created

  2. If you are installing Koperator on a Red Hat OpenShift cluster:

    1. Elevate the permissions of the Koperator namespace.

      • Using the default kafka namespace:

        oc adm policy add-scc-to-group anyuid system:serviceaccounts:kafka

      • Using a custom namespace for Koperator:

        oc adm policy add-scc-to-group anyuid system:serviceaccounts:{NAMESPACE_FOR_KOPERATOR}

      Expected output:

      clusterrole.rbac.authorization.k8s.io/system:openshift:scc:anyuid added: "system:serviceaccounts:{NAMESPACE_FOR_KOPERATOR}"

    2. If the Kafka cluster is going to run in a different namespace than Koperator , elevate the permissions of the Kafka cluster broker service account (ServiceAccountName provided in the KafkaCluster custom resource).

      oc adm policy add-scc-to-user anyuid system:serviceaccount:{NAMESPACE_FOR_KAFKA_CLUSTER_BROKER_SERVICE_ACCOUNT}:{KAFKA_CLUSTER_BROKER_SERVICE_ACCOUNT_NAME}

      Expected output:

      clusterrole.rbac.authorization.k8s.io/system:openshift:scc:anyuid added: "system:serviceaccount:{NAMESPACE_FOR_KAFKA_CLUSTER_BROKER_SERVICE_ACCOUNT}:{KAFKA_CLUSTER_BROKER_SERVICE_ACCOUNT_NAME}"

  3. Install Koperator into the kafka namespace:

    helm install \
kafka-operator \
--repo https://kubernetes-charts.banzaicloud.com kafka-operator \
--version 0.24.1 \
--namespace=kafka \
--create-namespace \
--atomic \
--debug

    Expected output:

    install.go:194: [debug] Original chart version: ""
install.go:211: [debug] CHART PATH: /Users/pregnor/development/src/github.com/banzaicloud/koperator/kafka-operator-0.24.1.tgz

# ...
NAME: kafka-operator
LAST DEPLOYED: Thu Mar 23 10:05:11 2023
NAMESPACE: kafka
STATUS: deployed
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
# ...

  4. Verify that Koperator has been deployed and is in running state.

    kubectl get pods -n kafka

    Expected output:

    NAME                                       READY   STATUS    RESTARTS   AGE
kafka-operator-operator-8458b45587-286f9   2/2     Running   0          62s

Deploy a Kafka cluster 🔗︎

  1. Create the Kafka cluster using the KafkaCluster custom resource. You can find various examples for the custom resource in KafkaCluster CR configuration and in the Koperator repository.

    CAUTION:

    After the cluster is created, you cannot change the way the listeners are configured without an outage. If a cluster is created with unencrypted (plain text) listener and you want to switch to SSL encrypted listeners (or the way around), you must manually delete each broker pod. The operator will restart the pods with the new listener configuration.

    • To create a sample Kafka cluster that allows unencrypted client connections, run the following command:

      kubectl create \
-n kafka \
-f https://raw.githubusercontent.com/banzaicloud/koperator/v0.24.1/config/samples/simplekafkacluster.yaml

    • To create a sample Kafka cluster that allows TLS-encrypted client connections, run the following command. For details on the configuration parameters related to SSL, see Enable SSL encryption in Apache Kafka.

      kubectl create \
-n kafka \
-f https://raw.githubusercontent.com/banzaicloud/koperator/v0.24.1/config/samples/simplekafkacluster_ssl.yaml

    Expected output:

    kafkacluster.kafka.banzaicloud.io/kafka created

  2. Wait and verify that the Kafka cluster resources have been deployed and are in running state.

    kubectl -n kafka get kafkaclusters.kafka.banzaicloud.io kafka --watch

    Expected output:

    NAME    CLUSTER STATE        CLUSTER ALERT COUNT   LAST SUCCESSFUL UPGRADE   UPGRADE ERROR COUNT   AGE
kafka   ClusterReconciling   0                                               0                     5s
kafka   ClusterReconciling   0                                               0                     7s
kafka   ClusterReconciling   0                                               0                     8s
kafka   ClusterReconciling   0                                               0                     9s
kafka   ClusterReconciling   0                                               0                     2m17s
kafka   ClusterReconciling   0                                               0                     3m11s
kafka   ClusterReconciling   0                                               0                     3m27s
kafka   ClusterReconciling   0                                               0                     3m29s
kafka   ClusterReconciling   0                                               0                     3m31s
kafka   ClusterReconciling   0                                               0                     3m32s
kafka   ClusterReconciling   0                                               0                     3m32s
kafka   ClusterRunning       0                                               0                     3m32s
kafka   ClusterReconciling   0                                               0                     3m32s
kafka   ClusterRunning       0                                               0                     3m34s
kafka   ClusterReconciling   0                                               0                     4m23s
kafka   ClusterRunning       0                                               0                     4m25s
kafka   ClusterReconciling   0                                               0                     4m25s
kafka   ClusterRunning       0                                               0                     4m27s
kafka   ClusterRunning       0                                               0                     4m37s
kafka   ClusterReconciling   0                                               0                     4m37s
kafka   ClusterRunning       0                                               0                     4m39s

    kubectl get pods -n kafka

    Expected output:

    kafka-0-9brj4                              1/1     Running   0          94s
kafka-1-c2spf                              1/1     Running   0          93s
kafka-2-p6sg2                              1/1     Running   0          92s
kafka-cruisecontrol-776f49fdbb-rjhp8       1/1     Running   0          51s
kafka-operator-operator-7d47f65d86-2mx6b   2/2     Running   0          13m

  3. If prometheus-operator is deployed, create a Prometheus instance and corresponding ServiceMonitors for Koperator .

    kubectl create \
-n kafka \
-f https://raw.githubusercontent.com/banzaicloud/koperator/v0.24.1/config/samples/kafkacluster-prometheus.yaml

    Expected output:

    clusterrole.rbac.authorization.k8s.io/prometheus created
clusterrolebinding.rbac.authorization.k8s.io/prometheus created
prometheus.monitoring.coreos.com/kafka-prometheus created
prometheusrule.monitoring.coreos.com/kafka-alerts created
serviceaccount/prometheus created
servicemonitor.monitoring.coreos.com/cruisecontrol-servicemonitor created
servicemonitor.monitoring.coreos.com/kafka-servicemonitor created

  4. Wait and verify that the Kafka cluster Prometheus instance has been deployed and is in running state.

    kubectl get pods -n kafka

    Expected output:

    NAME                                      READY   STATUS    RESTARTS   AGE
kafka-0-nvx8c                             1/1     Running   0          16m
kafka-1-swps9                             1/1     Running   0          15m
kafka-2-lppzr                             1/1     Running   0          15m
kafka-cruisecontrol-fb659b84b-7cwpn       1/1     Running   0          15m
kafka-operator-operator-8bb75c7fb-7w4lh   2/2     Running   0          17m
prometheus-kafka-prometheus-0             2/2     Running   0          16m

Test your deployment 🔗︎

Edit this page on GitHub