zookeeper-operator | Kubernetes Operator for Zookeeper | SDK library

Note: if you are running on Google Kubernetes Engine (GKE), please check this first. To understand how to deploy the zookeeper operator using helm, refer to this. Register the ZookeeperCluster custom resource definition (CRD). You can choose to enable Zookeeper operator for all namespaces or just for a specific namespace. The example is using the default namespace, but feel free to edit the Yaml files and use a different namespace. Create the operator role and role binding. Deploy the Zookeeper operator. Verify that the Zookeeper operator is running.
To understand how to upgrade the zookeeper cluster using helm, refer to this. To initiate an upgrade process manually, a user has to update the spec.image.tag field of the ZookeeperCluster custom resource. This can be done in three different ways using the kubectl command. After the tag field is updated, the StatefulSet will detect the version change and it will trigger the upgrade process. To detect whether a ZookeeperCluster upgrade is in progress or not, check the output of the command kubectl describe zk. Output of this command should contain the following entries. Additionally, the Desired Version will be set to the version that we are upgrading our cluster to.
kubectl edit zk <name>, modify the tag value in the YAML resource, save, and exit.
If you have the custom resource defined in a local YAML file, e.g. zk.yaml, you can modify the tag value, and reapply the resource with kubectl apply -f zk.yaml.
kubectl patch zk <name> --type='json' -p='[{"op": "replace", "path": "/spec/image/tag", "value": "X.Y.Z"}]'.
For upgrading the zookeeper operator check the document operator-upgrade.
Use the make command to build the Zookeeper operator image. That will generate a Docker image with the format <latest_release_tag>-<number_of_commits_after_the_release> (it will append-dirty if there are uncommitted changes). The image will also be tagged as latest. Example image after running make build. The Zookeeper operator image will be available in your Docker environment. Optionally push it to a Docker registry.
Go 1.13+
[REGISTRY_HOST] is your registry host or IP (e.g. registry.example.com)
[REGISTRY_PORT] is your registry port (e.g. 5000)
The Operator requires elevated privileges in order to watch for the custom resources.
To setup minikube locally you can follow the steps mentioned here. Once minikube setup is complete, minikube start will create a minikube VM. First install the zookeeper operator in either of the ways mentioned here. Since minikube provides a single node Kubernetes cluster which has a low resource provisioning, we provide a simple way to install a small zookeeper cluster on a minikube environment using the following command.