./demo- directorydocker-composeto run ZooKeeper, integration tests & backup-daemon../docs- directory with actual documentation for users and developers../operator/charts/helm/zookeeper-service- directory with main HELM chart with resources for ZooKeeper and integration tests../integration-tests- directory with Robot Framework test cases for ZooKeeper.
- Build operator and integration tests, if you need non-master versions.
- Prepare kubeconfig on you host machine to work with target cluster.
- Prepare
sample.yamlfile with deployment parameters, which should contains custom docker images if it is needed. - Store
sample.yamlfile incharts/helm/zookeeper-servicedirectory. - Go to
charts/helm/zookeeper-servicedirectory. - Run the following command:
helm install zookeeper-service ./ -f sample.yaml -n <TARGET_NAMESPACE>There is no smoke tests.
To debug zookeeper-operator in VSCode you can use Launch operator configuration which is already defined in
./.vscode/launch.json file.
The developer should configure environment variables: WATCH_NAMESPACE, KUBECONFIG.
Regarding KUBECONFIG, developer should need to define KUBECONFIG environment variable
which should contains path to the kube-config file. It can be defined on configuration level
or on the level of user's environment variables.
There are no well-defined rules for troubleshooting, as each task is unique, but there are some tips that can do:
- Deploy parameters.
- Application manifest.
- Logs from all ZooKeeper service pods: operator, ZooKeeper, monitoring, backup-daemon.
Also, developer can take a look on Troubleshooting guide.
To keep the component up to date, the following activities should be performed regularly:
- Vulnerabilities fixing.
- ZooKeeper upgrade.
- Bug-fixing, improvement and feature implementation for operator and other related supplementary services.