Stackable Operator for Apache ZooKeeper

Get started with Apache ZooKeeper and the Stackable operator by following the Getting started guide, it guides you through the installation process. Afterward, consult the Usage guide to learn more about configuring ZooKeeper for your needs. You can also deploy a demo to see an example deployment of ZooKeeper together with other data products.

The operator manages two custom resources: ZookeeperCluster and ZookeeperZnode. ZooKeeper only has a single process that it runs, so the cluster resource only has a single corresponding role called server.

For every role group the operator creates a ConfigMap and StatefulSet which can have multiple replicas (Pods). Every role group is accessible through its own Service, and there is a Service for the whole Cluster.

The operator creates a service discovery ConfigMap for the ZooKeeper instance, as well as for each ZNode. The discovery ConfigMaps contain information on how to connect to ZooKeeper. The ZNode discovery ConfigMap give access information for the ZNode. Learn more about ZNodes.

Apache ZooKeeper and the Stackable operator have no dependencies besides the Stackable Commons Operator, Stackable Secret Operator and Stackable Listener Operator.

Apache ZooKeeper is a dependency of Apache HBase, Apache Hadoop HDFS, Apache Kafka and Apache NiFi, thus any demo that uses one or more of these components also deploys a ZooKeeper ensemble. Here is the list of the demos that include ZooKeeper:

The Stackable operator for Apache ZooKeeper currently supports the ZooKeeper versions listed below. To use a specific ZooKeeper version in your ZookeeperCluster, you have to specify an image - this is explained in the Product image selection documentation. The operator also supports running images from a custom registry or running entirely customized images; both of these cases are explained under Product image selection as well.