What is Altinity.Cloud connect?
Altinity.Cloud connect (
altinitycloud-connect) is a tunneling daemon for Altinity.Cloud.
It enables management of ClickHouse clusters through Altinity.Cloud Anywhere.
altinitycloud-connect requires following permissions:
Open outbound ports:
- 443 tcp/udp (egress; stateful)
- cluster-admin for initial provisioning only, it can be revoked afterwards
- full access to ‘altinity-cloud-system’ and ‘altinity-cloud-managed-clickhouse’ namespaces and a few optional read-only cluster-level permissions (for observability)
Connecting to Altinity.Cloud
See the steps in the Quickstart Connect to Altinity.Cloud procedure.
Batch operation of altinitycloud-connect
altinitycloud-connect login produces
cloud-connect.pem used to connect to
Altinity.Cloud Anywhere control plane (
--token is short-lived while
cloud-connect.pem does not expire until revoked).
If you need to reconnect the environment in unattended/batch mode (i.e. without requesting the token),
you can do so via
altinitycloud-connect kubernetes -i /path/to/cloud-connect.pem | kubectl apply -f -
Disconnecting your environment from Altinity.Cloud
Locate your environment in the Environment tab in your Altinity.Cloud account.
Toggle the Delete Clusters switch only if you want to delete managed clusters.
Press OK to complete.
After this is complete Altinity.Cloud will no longer be able to see or connect to your Kubernetes environment via the connector.
Cleaning up managed environments in Kubernetes
To clean up managed ClickHouse installations and namespaces in a disconnected Kubernetes cluster, issue the following commands in the exact order shown below.
kubectl -n altinity-cloud-managed-clickhouse delete chi --all kubectl delete ns altinity-cloud-managed-clickhouse kubectl delete ns altinity-cloud-system
If you delete the namespaces before deleting the ClickHouse installations (chi) the operation will hang due to missing finalizers on chi resources. Should this occur, issue kubectl edit commands on each ClickHouse installation and remove the finalizer manually from the resource specification. Here is an example.
kubectl -n altinity-cloud-managed-clickhouse edit clickhouseinstallations.clickhouse.altinity.com/test2
Was this page helpful?
Glad to hear it!
Sorry to hear that. We'll track this issue and see how we can improve.