Running Altinity.Cloud in Your Kubernetes environment (BYOK)

Using your Kubernetes infrastructure

Running Altinity.Cloud in your Kubernetes environment (also known as Bring Your Own Kubernetes or BYOK) provides the convenient cloud management of Altinity.Cloud but lets you keep data within your own cloud VPCs and private data centers, all while running managed ClickHouse® in your own Kubernetes clusters. We sometimes call this Open Cloud for ClickHouse.

Benefits of Bring Your Own Kubernetes

Each Altinity.Cloud environment is a dedicated Kubernetes cluster. This approach has several important benefits:

  • Compliance - Retain full control of data (including backups) as well as the operating environment and impose your policies for security, privacy, and data sovereignty.
  • Cost - Optimize infrastructure costs by running in your accounts.
  • Location - Place ClickHouse clusters close to data sources and applications.
  • No vendor lock-in - Disconnect the control plane at any time and continue operating ClickHouse using open-source components.

When you’re running Altinity.Cloud in your Kubernetes environment, you’re using the open-source analytic stack and service architecture discussed on the Altinity.Cloud 101 page.

Configuring your Altinity.Cloud BYOK environment

To run Altinity.Cloud in your Kubernetes environment, you need to create your Kubernetes cluster and then use the Altinity Connector to establish a management from your Kubernetes cluster to Altinity.Cloud. The Altinity Connector establishes an outbound HTTPS connection to a management endpoint secured by certificates. This allows management commands and monitoring data to move securely between locations.

Configuring your BYOK environment is straightforward, and each step is covered in the pages of this section. The steps are:

  1. Make sure your Kubernetes cluster is configured properly. Configuration varies slightly from one cloud provider to another; the Kubernetes Requirements page has all the details.
  2. Connect Altinity.Cloud to your Kubernetes cluster. The Altinity Cloud Manager generates a one-time-use token that you use with the altinitycloud-connect utility. The Kubernetes environment connection page has all the details.
  3. Use the Environment Setup wizard to configure details such as availability zones, node types, and storage classes. All of those choices and options are explained on the connections page as well.

When the Environment Setup wizard is finished, you’re ready to create ClickHouse clusters inside your Kubernetes environment. Details of all those tasks as well as housekeeping tasks like configuring logging and configuring backups are all explained in the following pages:

Kubernetes requirements

Configuring your Kubernetes environment

Setting up EKS with Terraform for Altinity.Cloud

The easiest way to configure an EKS cluster

Connecting Your Kubernetes Environment to Altinity.Cloud

Tying everything together

Setting up logging

Configuring storage for logging

Setting up backups

Configuring storage for backups

Disconnecting from Altinity.Cloud

Using ClickHouse® without Altinity.Cloud

Deleting Managed ClickHouse® Environments in Kubernetes

Deleting your ClickHouse® cluster

Appendix: Using Altinity.Cloud with minikube

For testing and development use only