Run ZooKeeper as a data store for Kubernetes applications managed by Wodby.
This repository defines the Wodby service manifests and operational configuration for ZooKeeper.
| Property | Manifest configuration |
|---|---|
| Service name | zookeeper |
| Type | Datastore |
| Versions | 3.9 by default |
| Workloads | main (StatefulSet), primary |
| Containers | zookeeper using wodby/zookeeper |
| Endpoints | zookeeper: TCP 2181 |
| Volumes | Data, 5 GB |
| Helm | chart oci://registry-1.docker.io/wodby/zookeeper; version 0.2.1 |
Use this service through Drupal application stack, Solr application stack,
ZooKeeper application stack, or reference zookeeper from a custom Wodby stack.
A service is a reusable component and does not deploy by itself. The stack defines its links, settings, versions, resources, and relationship to the rest of the application.
- Fork this repository.
- Edit the service manifest and referenced files.
- Import the repository as a Git-backed service.
- Reference the service from a stack manifest.
Keep service, workload, container, endpoint, link, volume, config, and derivative names stable unless dependent stacks and app-level overrides are updated at the same time.
Validate the manifests with:
wodby service validate-manifest service.yml --org <org-id>See the service manifest reference and the managed services index.