Normally for my projects I use docker-compose + normal bind persistence directory to avoid data loss for database (and keep it fast and simple to maintain), because it's simpler to upgrade version than normal installation (looking at that popular database that annoying to upgrade the major version that requier a lot of copying) and the network/disk/cpu overhead also unnoticeable. Today we're gonna try to setup Clickhouse using minikube. Assuming you already installed minikube, all you need to do is install helm (k8s package manager).
curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get-helm-3 > install_helm.sh && bash install_helm.sh
helm install my-release oci://registry-1.docker.io/bitnamicharts/clickhouse
# to check again the deploy
helm status my-release
# to check configurable options
helm show all oci://registry-1.docker.io/bitnamicharts/clickhouse
# to uninstall
helm uninstall my-release
by default it would create 2 shard with 3 replica (includes the pv and pvc for all pods), and too bad it's still using zookeeper instead of clickhouse-keeper.
my-release-clickhouse-shard0-0 1/1 Running 0
my-release-clickhouse-shard0-1 1/1 Running 0
my-release-clickhouse-shard0-2 1/1 Running 0
my-release-clickhouse-shard1-0 1/1 Running 0
my-release-clickhouse-shard1-1 1/1 Running 0
my-release-clickhouse-shard1-2 1/1 Running 0
my-release-zookeeper-0 1/1 Running 0
my-release-zookeeper-1 1/1 Running 0
my-release-zookeeper-2 1/1 Running 0
to access it locally you just need to port forward and connect using clickhouse-client program:
kubectl port-forward --namespace default svc/my-release-clickhouse 9001:9000 &
clickhouse-client --host localhost --port 9001 --user default --password $(kubectl get secret --namespace default my-release-clickhouse -o jsonpath="{.data.admin-password}" | base64 -d)
alternatively you can just exec into the pod and use clickhouse-client inside the pod:
kubectl exec -it my-release-clickhouse-shard1-2 sh
clickhouse-client # use password from above
you already can create distributed table and do stuff with it. For more information about bitnami charts you can read it here. If you want to customize your setup (not 2 shard 3 replica, I always prefer no shard but multiple replica, unless your data is massive that hard not to shard across multiple machines). You can clone the chart and the modify the configuration, then deploy it, something like this:
git clone --depth 1 git@github.com:bitnami/charts.git
vim charts/bitnami/clickhouse/values.yaml
# ^ change shard=1 keeper.enabled=true zookeeper.enabled=false
helm dependency build charts/bitnami/clickhouse
helm install ch1 charts/bitnami/clickhouse
# update
helm upgrade ch1 charts/bitnami/clickhouse
it would create something like this:
ch1-clickhouse-shard0-0 1/1 Running 0
ch1-clickhouse-shard0-1 1/1 Running 0
ch1-clickhouse-shard0-2 1/1 Running 0
That's it for now, not sure how to run this in real kubernetes cluster (not minikube), especially making the pv/pvc to be put in multiple nodes.