Installing the ClickHouse Operator and Cluster on OpenShift and Kubernetes: A Step-by-Step Guide
Nowadays, managing and storing data is one of the most important parts of any company, and database evolution is a movement that happens every day. There are many databases that play an important role in a company's stack, so we should choose the one that best fits our use case. As a DevOps engineer, we need to prepare the environment to develop and run them. In this document, I want to share my…
In today's data-driven world, selecting an appropriate database is crucial for any company. This guide demonstrates how to deploy the ClickHouse operator and a ClickHouse cluster on both OpenShift and Kubernetes platforms. Two methods are outlined: installation through the OpenShift console and installation using the ClickHouse official Helm chart.
The OpenShift console approach offers a straightforward installation process with minimal customization. After logging into OpenShift with administrator privileges, search for the ClickHouse operator in the Software Catalog. Once located, click the Install button and specify the desired version and namespace for the operator installation.
The system will then pull the operator image and set up the necessary Custom Resource Definitions (CRDs) on the cluster. After approval, the operator becomes ready and can be used to define the ClickHouse cluster and Keeper configuration.
An alternative method involves using the ClickHouse official Helm chart. This approach involves rendering the manifests locally with Helm, taking into account the target namespace where the ClickHouse clusters will operate. If the cluster lacks internet access, edit the Deployment's container arguments to disable automatic version checks.
Deploy the manifests using oc, and monitor the operator pod's status. Once the operator is operational, create the ClickHouse cluster by applying a ClickHouseInstallation (CHI) manifest describing the desired configuration. Utilize the OpenShift web console or the command-line interface (CLI) to verify the successful deployment of the ClickHouse cluster and check the status of associated pods and services.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — it may contain errors, so check the original before relying on it.
