Upgrade Guide

How to upgrade the Altinity Kubernetes Operator for ClickHouse®

The Altinity Kubernetes Operator for ClickHouse® can be upgraded at any time by applying the new manifest from the operator's repository.

The following procedures detail how to install a specific version of the operator in the default Kubernetes namespace kube-system. For instructions on performing custom installations based on the namespace and other settings, see the Custom Installation Guide.

Requirements

The Altinity Kubernetes Operator for ClickHouse has the following requirements:

Kubernetes 1.15.11+. For instructions on how to install Kubernetes for your particular environment, see the Kubernetes Install Tools page.
Access to the Altinity Kubernetes Operator GitHub repository.

Instructions

The following instructions are based on installations of the operator greater than version 0.16.0. In the following examples, version 0.16.0 has been installed and will be upgraded to 0.18.3.

For instructions on installing specific versions of the operator, see the Specific Version Installation Guide.

Deploy the Altinity Kubernetes Operator for ClickHouse from the manifest directly from GitHub. It is recommended that the version be specified during the installation for maximum compatibility. In this example, the version being upgraded to is 0.18.3:
```
kubectl apply -f https://github.com/Altinity/clickhouse-operator/raw/0.18.3/deploy/operator/clickhouse-operator-install-bundle.yaml
```

The following will be displayed on a successful installation. For more information on the resources created in the installation, see the operator resources guide.

customresourcedefinition.apiextensions.k8s.io/clickhouseinstallations.clickhouse.altinity.com configured
customresourcedefinition.apiextensions.k8s.io/clickhouseinstallationtemplates.clickhouse.altinity.com configured
customresourcedefinition.apiextensions.k8s.io/clickhouseoperatorconfigurations.clickhouse.altinity.com configured
serviceaccount/clickhouse-operator configured
clusterrole.rbac.authorization.k8s.io/clickhouse-operator-kube-system configured
clusterrolebinding.rbac.authorization.k8s.io/clickhouse-operator-kube-system configured
configmap/etc-clickhouse-operator-files configured
configmap/etc-clickhouse-operator-confd-files configured
configmap/etc-clickhouse-operator-configd-files configured
configmap/etc-clickhouse-operator-templatesd-files configured
configmap/etc-clickhouse-operator-usersd-files configured
deployment.apps/clickhouse-operator configured
service/clickhouse-operator-metrics configured

Verify the installation by running:

The following will be displayed on a successful installation, with your particular image:

kubectl get pods --namespace kube-system

NAME                                   READY   STATUS    RESTARTS       AGE
clickhouse-operator-857c69ffc6-dqt5l   2/2     Running   0              29s
coredns-78fcd69978-nthp2               1/1     Running   3 (14d ago)    50d
etcd-minikube                          1/1     Running   3 (14d ago)    50d
kube-apiserver-minikube                1/1     Running   3 (2m6s ago)   50d
kube-controller-manager-minikube       1/1     Running   3 (14d ago)    50d
kube-proxy-lsggn                       1/1     Running   3 (14d ago)    50d
kube-scheduler-minikube                1/1     Running   3 (2m6s ago)   50d
storage-provisioner                    1/1     Running   7 (48s ago)    50d

To verify the version of the operator, use the following command:

kubectl get pods -l app=clickhouse-operator -n kube-system -o jsonpath="{.items[*].spec.containers[*].image}" | tr -s "[[:space:]]" | sort | uniq -c

1 altinity/clickhouse-operator:0.18.3 altinity/metrics-exporter:0.18.3