Overview
KubeDB is the Kubernetes Native Database Management Solution which simplifies and automates routine database tasks such as Provisioning, Monitoring, Upgrading, Patching, Scaling, Volume Expansion, Backup, Recovery, Failure detection, and Repair for various popular databases on private and public clouds. The databases supported by KubeDB include MongoDB, Elasticsearch, MySQL, MariaDB, Redis, PostgreSQL, FerretDB, Percona XtraDB, and Memcached. Additionally, KubeDB also supports ProxySQL, PgBouncer, Pgpool, ZooKeeper and the streaming platform Kafka, RabbitMQ. You can find the guides to all the supported databases in KubeDB . In this tutorial we will deploy ZooKeeper in Amazon Elastic Kubernetes Service (Amazon EKS). We will cover the following steps:
- Install KubeDB
- Deploy ZooKeeper
- Access/Create Sample Node
Get Cluster ID
We need the cluster ID to get the KubeDB License. To get cluster ID we can run the following command:
$ kubectl get ns kube-system -o jsonpath='{.metadata.uid}'
8e336615-0dbb-4ae8-b72f-2e7ec34c399d
Get License
Go to Appscode License Server to get the license.txt file. For this tutorial we will use KubeDB.
Install KubeDB
We will use helm to install KubeDB. Please install helm here
if it is not already installed.
Now, let’s install KubeDB.
$ helm search repo appscode/kubedb
NAME CHART VERSION APP VERSION DESCRIPTION
appscode/kubedb v2024.4.27 v2024.4.27 KubeDB by AppsCode - Production ready databases...
appscode/kubedb-autoscaler v0.30.0 v0.30.0 KubeDB Autoscaler by AppsCode - Autoscale KubeD...
appscode/kubedb-catalog v2024.4.27 v2024.4.27 KubeDB Catalog by AppsCode - Catalog for databa...
appscode/kubedb-community v0.24.2 v0.24.2 KubeDB Community by AppsCode - Community featur...
appscode/kubedb-crd-manager v0.0.9 v0.0.9 KubeDB CRD Manager by AppsCode
appscode/kubedb-crds v2024.4.27 v2024.4.27 KubeDB Custom Resource Definitions
appscode/kubedb-dashboard v0.21.0 v0.21.0 KubeDB Dashboard by AppsCode
appscode/kubedb-enterprise v0.11.2 v0.11.2 KubeDB Enterprise by AppsCode - Enterprise feat...
appscode/kubedb-grafana-dashboards v2024.4.27 v2024.4.27 A Helm chart for kubedb-grafana-dashboards by A...
appscode/kubedb-kubestash-catalog v2024.4.27 v2024.4.27 KubeStash Catalog by AppsCode - Catalog of Kube...
appscode/kubedb-metrics v2024.4.27 v2024.4.27 KubeDB State Metrics
appscode/kubedb-one v2023.12.28 v2023.12.28 KubeDB and Stash by AppsCode - Production ready...
appscode/kubedb-ops-manager v0.32.0 v0.32.1 KubeDB Ops Manager by AppsCode - Enterprise fea...
appscode/kubedb-opscenter v2024.4.27 v2024.4.27 KubeDB Opscenter by AppsCode
appscode/kubedb-provider-aws v2024.4.27 v0.7.0 A Helm chart for KubeDB AWS Provider for Crossp...
appscode/kubedb-provider-azure v2024.4.27 v0.7.0 A Helm chart for KubeDB Azure Provider for Cros...
appscode/kubedb-provider-gcp v2024.4.27 v0.7.0 A Helm chart for KubeDB GCP Provider for Crossp...
appscode/kubedb-provisioner v0.45.0 v0.45.1 KubeDB Provisioner by AppsCode - Community feat...
appscode/kubedb-schema-manager v0.21.0 v0.21.0 KubeDB Schema Manager by AppsCode
appscode/kubedb-ui v2024.5.17 0.6.8 A Helm chart for Kubernetes
appscode/kubedb-ui-server v2021.12.21 v2021.12.21 A Helm chart for kubedb-ui-server by AppsCode
appscode/kubedb-webhook-server v0.21.0 v0.21.1 KubeDB Webhook Server by AppsCode
$ helm install kubedb oci://ghcr.io/appscode-charts/kubedb \
--version v2024.4.27 \
--namespace kubedb --create-namespace \
--set-file global.license=/path/to/the/license.txt \
--set global.featureGates.ZooKeeper=true \
--wait --burst-limit=10000 --debug
Let’s verify the installation:
$ watch kubectl get pods --all-namespaces -l "app.kubernetes.io/instance=kubedb"
NAMESPACE NAME READY STATUS RESTARTS AGE
kubedb kubedb-kubedb-autoscaler-784d7d8d9b-f66nn 1/1 Running 0 3m27s
kubedb kubedb-kubedb-ops-manager-78f4d6d4d4-bcdp5 1/1 Running 0 3m27s
kubedb kubedb-kubedb-provisioner-79799cb478-rjvpw 1/1 Running 0 3m27s
kubedb kubedb-kubedb-webhook-server-77bcf46f5c-ng9sr 1/1 Running 0 3m27s
kubedb kubedb-petset-operator-5d94b4ddb8-tzld4 1/1 Running 0 3m27s
kubedb kubedb-petset-webhook-server-5f599778bf-fllkx 2/2 Running 0 3m27s
kubedb kubedb-sidekick-5d9947bd9-fmt5j 1/1 Running 0 3m27s
We can list the CRD Groups that have been registered by the operator by running the following command:
$ kubectl get crd -l app.kubernetes.io/name=kubedb
NAME CREATED AT
connectclusters.kafka.kubedb.com 2024-05-21T10:57:05Z
connectors.kafka.kubedb.com 2024-05-21T10:57:05Z
druidversions.catalog.kubedb.com 2024-05-21T10:56:06Z
elasticsearchautoscalers.autoscaling.kubedb.com 2024-05-21T10:57:02Z
elasticsearchdashboards.elasticsearch.kubedb.com 2024-05-21T10:57:02Z
elasticsearches.kubedb.com 2024-05-21T10:57:02Z
elasticsearchopsrequests.ops.kubedb.com 2024-05-21T10:57:02Z
elasticsearchversions.catalog.kubedb.com 2024-05-21T10:56:06Z
etcdversions.catalog.kubedb.com 2024-05-21T10:56:06Z
ferretdbversions.catalog.kubedb.com 2024-05-21T10:56:06Z
kafkaautoscalers.autoscaling.kubedb.com 2024-05-21T10:57:05Z
kafkaconnectorversions.catalog.kubedb.com 2024-05-21T10:56:06Z
kafkaopsrequests.ops.kubedb.com 2024-05-21T10:57:05Z
kafkas.kubedb.com 2024-05-21T10:57:05Z
kafkaversions.catalog.kubedb.com 2024-05-21T10:56:06Z
mariadbarchivers.archiver.kubedb.com 2024-05-21T10:57:08Z
mariadbautoscalers.autoscaling.kubedb.com 2024-05-21T10:57:08Z
mariadbdatabases.schema.kubedb.com 2024-05-21T10:57:08Z
mariadbopsrequests.ops.kubedb.com 2024-05-21T10:57:08Z
mariadbs.kubedb.com 2024-05-21T10:57:08Z
mariadbversions.catalog.kubedb.com 2024-05-21T10:56:06Z
memcachedversions.catalog.kubedb.com 2024-05-21T10:56:06Z
mongodbarchivers.archiver.kubedb.com 2024-05-21T10:57:12Z
mongodbautoscalers.autoscaling.kubedb.com 2024-05-21T10:57:12Z
mongodbdatabases.schema.kubedb.com 2024-05-21T10:57:12Z
mongodbopsrequests.ops.kubedb.com 2024-05-21T10:57:12Z
mongodbs.kubedb.com 2024-05-21T10:57:12Z
mongodbversions.catalog.kubedb.com 2024-05-21T10:56:06Z
mssqlserverversions.catalog.kubedb.com 2024-05-21T10:56:06Z
mysqlarchivers.archiver.kubedb.com 2024-05-21T10:57:15Z
mysqlautoscalers.autoscaling.kubedb.com 2024-05-21T10:57:15Z
mysqldatabases.schema.kubedb.com 2024-05-21T10:57:15Z
mysqlopsrequests.ops.kubedb.com 2024-05-21T10:57:15Z
mysqls.kubedb.com 2024-05-21T10:57:15Z
mysqlversions.catalog.kubedb.com 2024-05-21T10:56:06Z
perconaxtradbversions.catalog.kubedb.com 2024-05-21T10:56:06Z
pgbouncerversions.catalog.kubedb.com 2024-05-21T10:56:06Z
pgpoolversions.catalog.kubedb.com 2024-05-21T10:56:06Z
postgresarchivers.archiver.kubedb.com 2024-05-21T10:57:19Z
postgresautoscalers.autoscaling.kubedb.com 2024-05-21T10:57:19Z
postgresdatabases.schema.kubedb.com 2024-05-21T10:57:19Z
postgreses.kubedb.com 2024-05-21T10:57:18Z
postgresopsrequests.ops.kubedb.com 2024-05-21T10:57:19Z
postgresversions.catalog.kubedb.com 2024-05-21T10:56:06Z
proxysqlversions.catalog.kubedb.com 2024-05-21T10:56:06Z
publishers.postgres.kubedb.com 2024-05-21T10:57:19Z
rabbitmqversions.catalog.kubedb.com 2024-05-21T10:56:06Z
redisautoscalers.autoscaling.kubedb.com 2024-05-21T10:57:22Z
redises.kubedb.com 2024-05-21T10:57:22Z
redisopsrequests.ops.kubedb.com 2024-05-21T10:57:22Z
redissentinelautoscalers.autoscaling.kubedb.com 2024-05-21T10:57:22Z
redissentinelopsrequests.ops.kubedb.com 2024-05-21T10:57:22Z
redissentinels.kubedb.com 2024-05-21T10:57:22Z
redisversions.catalog.kubedb.com 2024-05-21T10:56:07Z
singlestoreversions.catalog.kubedb.com 2024-05-21T10:56:07Z
solrversions.catalog.kubedb.com 2024-05-21T10:56:07Z
subscribers.postgres.kubedb.com 2024-05-21T10:57:19Z
zookeepers.kubedb.com 2024-05-21T10:57:25Z
zookeeperversions.catalog.kubedb.com 2024-05-21T10:56:07Z
Deploy ZooKeeper
Now, we are going to Deploy ZooKeeper using KubeDB. First, let’s create a Namespace in which we will deploy the ZooKeeper.
$ kubectl create namespace demo
namespace/demo created
Here is the yaml of the ZooKeeper CRO we are going to use:
apiVersion: kubedb.com/v1alpha2
kind: ZooKeeper
metadata:
name: zookeeper
namespace: demo
spec:
version: "3.9.1"
adminServerPort: 8080
replicas: 3
storage:
resources:
requests:
storage: "1Gi"
storageClassName: "gp2"
accessModes:
- ReadWriteOnce
terminationPolicy: "WipeOut"
Let’s save this yaml configuration into zookeeper.yaml
Then create the above ZooKeeper CRO,
$ kubectl apply -f zookeeper.yaml
zookeeper.kubedb.com/zookeeper created
In this yaml,
spec.versionfield specifies the version of ZooKeeper Here, we are using ZooKeeperversion 3.9.1. You can list the KubeDB supported versions of ZooKeeper by running$ kubectl get zookeeperversionscommand.spec.storagespecifies PVC spec that will be dynamically allocated to store data for this database. This storage spec will be passed to the StatefulSet created by KubeDB operator to run database pods. You can specify any StorageClass available in your cluster with appropriate resource requests.- And the
spec.terminationPolicyfield is Wipeout means that the database will be deleted without restrictions. It can also be “Halt”, “Delete” and “DoNotTerminate”.
Once these are handled correctly and the ZooKeeper object is deployed, you will see that the following objects are created:
$ kubectl get all -n demo
NAME READY STATUS RESTARTS AGE
pod/zookeeper-0 1/1 Running 0 3m28s
pod/zookeeper-1 1/1 Running 0 86s
pod/zookeeper-2 1/1 Running 0 78s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/zookeeper ClusterIP 10.96.106.95 <none> 2181/TCP 3m36s
service/zookeeper-admin-server ClusterIP 10.96.58.77 <none> 8080/TCP 3m36s
service/zookeeper-pods ClusterIP None <none> 2181/TCP,2888/TCP,3888/TCP 3m36s
NAME TYPE VERSION AGE
appbinding.appcatalog.appscode.com/zookeeper kubedb.com/zookeeper 3.9.1 3m36s
Let’s check if the ZooKeeper is ready to use,
$ kubectl get zookeeper -n demo zookeeper
NAME TYPE VERSION STATUS AGE
zookeeper kubedb.com/v1alpha2 3.9.1 Ready 4m37s
We have successfully deployed ZooKeeper in Amazon EKS. Now we can exec into the container to use the database.
Create Sample Node
In this section, we are going to exec into our ZooKeeper pod and create a sample node.
$ kubectl exec -it -n demo zookeeper-0 -- sh
$ echo ruok | nc localhost 2181
imok
$ zkCli.sh create /product kubedb
Connecting to localhost:2181
...
Connection Log Messeges
...
Created /product
$ zkCli.sh get /product
Connecting to localhost:2181
...
Connection Log Messeges
...
kubedb
We’ve successfully access ZooKeeper and create a sample ZooKeeper node. More information about Deploy & Manage Production-Grade ZooKeeper on Kubernetes can be found in ZooKeeper Kubernetes
We have made an in depth tutorial on Provision and Manage ZooKeeper Ensemble on Kubernetes using KubeDB. You can have a look into the video below:
Support
To speak with us, please leave a message on our website .
To receive product announcements, follow us on X .
To watch tutorials of various Production-Grade Kubernetes Tools Subscribe our YouTube channel.
More about ZooKeeper on Kubernetes
If you have found a bug with KubeDB or want to request for new features, please file an issue .