This is the multi-page printable view of this section. Click here to print.
Altinity.Cloud Anywhere is a zero-maintenance, open source-based SaaS for ClickHouse that gives you control of your data, letting you chart your own path and giving you choice as to working with vendors or running your infrastructure yourself.
Your data. Your control. Our tools.
17 May 2023 · Read time 4 min
Altinity.Cloud Anywhere provides the convenient cloud management of Altinity.Cloud but allows users to keep data within their own cloud VPCs and private data centers, and run managed ClickHouse in their own Kubernetes clusters. We call these clusters Altinity.Cloud Anywhere environments.
Altinity.Cloud Anywhere offers several important benefits for users.
The rest of this document explains concepts that help users understand Altinity.Cloud Anywhere and maximize benefits.
The Altinity.Cloud Manager UI manages Altinity.Cloud Anywhere environments are just like fully hosted Altinity.Cloud environments. Users can control multiple environments from the same Altinity.Cloud account and can mix/match environment types. ClickHouse management operations are identical in all environments.
The Altinity.Cloud service architecture consists of a shared management plane that serves as a single point of management for all tenants and a data plane that consists of isolated environments for each tenant. The following diagram shows the service architecture and data plane relationships.
Each environment is a dedicated Kubernetes cluster. In the case of Altinity.Cloud environments, Kubernetes clusters run on Altinity’s cloud accounts and are completely hidden from users. In the Altinity.Cloud Anywhere case, Kubernetes clusters run in the user’s cloud account or data center.
For example, the user may run an EKS cluster within a VPC belonging to the user’s AWS cloud account.
Altinity.Cloud Anywhere environments can also use on-prem Kubernetes clusters. They can even use development versions of Kubernetes running on a user’s PC or laptop.
Altinity.Cloud Anywhere uses open-source software for the analytic stack and selected management services–the Altinity Operator for ClickHouse, Prometheus, and Grafana. The following diagram shows how the principal components map to resources in AWS. (GCP is essentially identical.) Open-source components are marked in orange.
Users can terminate the service, and disconnect the Altinity.Cloud Anywhere environment from Altinity.Cloud, and run ClickHouse services themselves. There is no migration, since all data, software, and support services are already in the user Kubernetes cluster.
Altinity.Cloud Anywhere environments use the Altinity Connector to establish a management connection from the user 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.
Users connect an Altinity.Cloud Anywhere environment to Altinity.Cloud in three simple steps.
Altinity.Cloud Anywhere environments run all services in two namespaces.
See the Quickstart page for steps to register an Altinity.Cloud Anywhere environment.
Kubernetes clusters must meet a small number of requirements to serve as an Altinity.Cloud Anywhere environment for production use.
These requirements can be relaxed for non-production environments, such as Minikube. Check the Kubernetes Requirements page for more recommendations on specific Kubernetes distributions.
In Altinity.Cloud Anywhere environments the responsibility for administration is shared between Altinity and users. The following table shows major system components.
Altinity is developing a new model called Altinity.Cloud Anywhere Plus. It will shift responsibility for Kubernetes and VPC management to Altinity. Contact Altinity Support for more information on this model.
This tutorial explains how to use Altinity.Cloud Anywhere to deploy ClickHouse clusters using your choice of a third-party Kubernetes cloud provider, or using your own hardware or private company cloud. The Altinity.Cloud Manager (ACM) is used to manage your ClickHouse clusters.
More Information
If you encounter difficulties with any part of the tutorial, check the Troubleshooting section. Contact Altinity support for additional help if the troubleshooting advice does not resolve the problem.
Altinity.Cloud Anywhere supports the following Kubernetes environments:
The following guidelines are provided to help you create your Kubernetes cluster.
For non-production use, a Minikube-based tutorial is provided to show how to use an Altinity.Cloud Anywhere deployment on a home computer. This is a 20-minute read that includes creating a new database and adding tables and data using the ACM.
Get your Altinity.Cloud Anywhere free trial account from the following link and fill in the information:
Submitting the Free Trial form
Now you are ready to connect your Kubernetes cluster.
The first time you log in, you will be directed to the environment setup page shown in Figure 3. If you have an existing account or restart the installation, just select the Environments tab on the left side of your screen to reach the setup page.
Highlighted in red in Figure 3 are the steps to complete before you select the PROCEED button.
In the first step labeled Altinity.Cloud connect, download the correct binary for your system.
In step 2 Connect to Altinity.Cloud, copy and paste the connection string to your terminal. Note that there is no output, so the command prompt is immediately ready for the next command.
altinitycloud-connect login --token=<registration token>
Run the Deploy connector to your Kubernetes cluster command.
altinitycloud-connect kubernetes | kubectl apply -f -
This step takes several minutes to complete depending on the speed of your host system.
The response displays as follows:
namespace/altinity-cloud-system created
namespace/altinity-cloud-managed-clickhouse created
clusterrole.rbac.authorization.k8s.io/altinity-cloud:node-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:node-metrics-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:storage-class-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:persistent-volume-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:cloud-connect unchanged
serviceaccount/cloud-connect created
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:cloud-connect unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:node-view unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:node-metrics-view unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:storage-class-view unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:persistent-volume-view unchanged
rolebinding.rbac.authorization.k8s.io/altinity-cloud:cloud-connect created
rolebinding.rbac.authorization.k8s.io/altinity-cloud:cloud-connect created
secret/cloud-connect created
deployment.apps/cloud-connect created
Note: In order to display Kubernetes roles and resources before applying run the following command.
altinitycloud-connect kubernetes
Once these commands have completed select the PROCEED button. After the connection is made, you will advance to the next Resources Configuration screen.
At the Resources Configuration screen, set the resources used for ClickHouse clusters as follows.
The following Resources Configuration example shows the red boxes around the settings made for the Google Cloud Platform GKE environment.
Zone Instance Type Capacity Used for
--------- -------------- -------- ---------------------------------------------------
us-east-b e2-standard-2 10 [True] ClickHouse [True] Zookeeper [False] System
us-east-a e2-standard-2 3 [True] ClickHouse [True] Zookeeper [False] System
The Confirmation screen displays a JSON representation of the settings you just made. Review these settings then select FINISH.
Once the connection is fully set up, the ACM Environments dashboard will display your new environment as shown in Figure 5 (example: cloudv2gpc).
To create your first cluster, switch to the Cluster page as indicated by the red keylines in Figure 6:
The Cluster Launch Wizard document covers how to create a new cluster.
The result shown in Figure 6 is a ClickHouse cluster added to the Clusters dashboard.
Figure 6 - The result: The ACM displays a new ClickHouse cluster (Example cluster name: free-trial-any) deployed by Altinity.Cloud Anywhere.
Problem
The altinitycloud-connect command has a –url option that defaults to host anywhere.altinity.cloud on port 443. If this host is not reachable, the following error message appears.
altinitycloud-connect login --token=<token>
Error: Post "https://anywhere.altinity.cloud/sign":
dial tcp: lookup anywhere.altinity.cloud on 127.0.0.53:53: no such host
Solution
Make sure the name is available in DNS and that the resolved IP address is reachable on port 443 (UDP and TCP), then try again.
Note: if you are using a non-production Altinity.Cloud environment you must specify the correct URL explicitly. Contact Altinity support for help.
Problem
Solution
Set the following permissions for your Kubernetes account:
altinity-cloud-system and altinity-cloud-managed-clickhouse namespacesProblem
Solution
When you reboot your Mac, the Anywhere cluster in your ACM has not started.
Problem
One of the pods won’t start. (Example: see line 3 edge-proxy-66d44f7465-lxjjn)
┌──────────────── Pods(altinity-cloud-system)[8] ──────────────────────────┐
│ NAME↑ PF READY RESTARTS STATUS │
1 │ cloud-connect-d6ff8499f-bkc5k ● 1/1 3 Running │
2 │ crtd-665fd5cb85-wqkkk ● 1/1 3 Running │
3 │ edge-proxy-66d44f7465-lxjjn ● 1/2 7 CrashLoopBackOff │
4 │ grafana-5b466574d-4scjc ● 1/1 1 Running │
5 │ kube-state-metrics-58d86c747c-7hj79 ● 1/1 6 Running │
6 │ node-exporter-762b5 ● 1/1 3 Running │
7 │ prometheus-0 ● 1/1 3 Running │
8 │ statuscheck-f7c9b4d98-2jlt6 ● 1/1 3 Running │
└──────────────────────────────────────────────────────────────────────────┘
Terminal listing 1 - The pod in Line 3 edge-proxy-66d44f7465-lxjjn won’t start.
Solution
Delete the pod using the kubectl delete pod command and it will regenerate. (Example: see line 3 edge-proxy-66d44f7465-lxjjn)
kubectl -n altinity-cloud-system delete pod edge-proxy-66d44f7465-lxjjn
Altinity.Cloud Anywhere operates inside user’s Kubernetes environment. Kubernetes can be provisioned by Altinity or provided by a user as described in the following section:
Kubernetes installation should satisfy the following criteria in order to work for Altinity.Cloud:
Following Kubernetes capabilities are preferrable in order to get the most from Altinity.Cloud features:
See cloud specific requirements in the following sections:
20 March 2023 · Read time 1 min
We recommend setting up karpenter or cluster-autoscaler to launch instances in at least 3 Availability Zones.
If you plan on sharing Kubernetes cluster with other workloads, it’s
recommended you label Kubernetes Nodes intended for Altinity.Cloud Anywhere
with altinity.cloud/use=anywhere & taint with dedicated=anywhere:NoSchedule.
t3.large or t4g.large** t4g instances are AWS Graviton2-based (ARM).
ClickHouse works the best in AWS when using nodes from those instance families:
m5m6im6g** m6g instances are AWS Graviton2-based (ARM).
Instance sizes from large to 8xlarge are typical.
gp2gp2-encryptedgp3*gp3-encrypted** gp3 storage classes require Amazon EBS CSI driver that does not come pre-installed.
Example manifests:
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: gp2
provisioner: kubernetes.io/aws-ebs
parameters:
fsType: ext4
type: gp2
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: true
---
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: gp2-encrypted
provisioner: kubernetes.io/aws-ebs
parameters:
encrypted: 'true'
fsType: ext4
type: gp2
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: true
---
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: gp3
provisioner: ebs.csi.aws.com
parameters:
fsType: ext4
type: gp3
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: true
---
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: gp3-encrypted
annotations:
storageclass.kubernetes.io/is-default-class: 'true'
provisioner: ebs.csi.aws.com
parameters:
encrypted: 'true'
fsType: ext4
type: gp3
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: true
Notes:
---
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: gp3-encrypted-500
provisioner: ebs.csi.aws.com
parameters:
encrypted: 'true'
fsType: ext4
throughput: '500'
type: gp3
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: true
20 March 2023 · Read time 1 min
NOTE: Depending on machine types & number of instances you plan to use, you may need to request GCE quota increase.
From the table, filter on the Quota (example: persistent Disk SSD) and Dimensions (example: specify the region name us-west1) columns, select EDIT QUOTAS then change the Limit value (example: change 500 GB to 600 GB).
Property name filter example
Altinity recommends setting up each node pool except the default one in at least 3 zones.
If you plan on sharing Kubernetes cluster with other workloads, it’s
recommended you label Kubernetes Nodes intended for Altinity.Cloud Anywhere
with altinity.cloud/use=anywhere & taint with dedicated=anywhere:NoSchedule.
e2-standard-2It’s recommended to taint node pools below with dedicated=clickhouse:NoSchedule (in addition to altinity.cloud/use=anywhere).
n2d-standard-2n2d-standard-4n2d-standard-8n2d-standard-16n2d-standard-32If GCP is out of n2d-standard-* instances in the region of your choice, we recommend
substituting them with n2-standard-*.
standard-rwopremium-rwoGKE comes pre-configured with both.
End-to-end instructions that show you how to install Kubernetes clusters for Altinity.Cloud Anywhere on Amazon (EKS), Google (GKS) or Minikube running on Docker. This include instructions on how to use the Altinity Cloud Manager to create a ClickHouse cluster in your Altinity.Cloud Anywhere Kubernetes installation.
10 May 2023 · Read time 6 min
Altinity.Cloud Anywhere operates inside user’s Kubernetes environment.
Kubernetes can be provided by a user (see “Kubernetes Installation” section), or provisioned by Altinity.
Altinity technical support can remotely provision AWS EKS clusters with an Altinity.Cloud Anywhere environment on your Amazon account. Instructions on this page describe how to configure your EKS clusters to provide permission to Altinity to provision ClickHouse to your Amazon EKS Kubernetes environment. Shown in Figure 1 is a high level view that shows the Altinity.Cloud Kubernetes infrastructure.
This section summarizes the bootstrap process so that you can use Altinity.Cloud to deploy a ClickHouse cluster to your AWS EKS environment.
Follow the Altinity.Cloud Anywhere Quickstart.
Provision an AWS EKS cluster using EC2 instance running with a user account.
The EC2 instance is required in order to deploy altinitycloud-connect, which will establish an outbound connection to Altinity.Cloud and start the EKS provisioning process.
The EC2 instance can be set up in two ways:
Follow this document to complete the provisioning process.
In the Altinity Cloud Manager, complete the configuration of EKS resources.
An Amazon AWS EC2 instance is required to deploy altinitycloud-connect, which will establish an outbound connection to Altinity.Cloud and start the EKS provisioning process.
In Altinity.Cloud
Get an Altinity.Cloud account.
Get an Altinity.Cloud Anywhere environment record.
Get the connection token from Altinity Cloud Manager connection wizard.
us-west-2.console.aws.amazon.com/cloudformation/home?region=us-west-2#/stacks/create
altinitycloud-connect-<releasу-tag>.aws-cloudformation.yaml
Choose Upload a template file and select the Altinity Cloud Formation Template YAML file as shown in Figure 2.
Fill missing fields on Specify Stack Details page:
Set ‘Stack Name’ to: NOTE: (replace $USER and the $ENV_NAME as needed) altinitycloud-connect-$USER-$ENV_NAME
Set ‘Subnets’ where altinitycloud-connect EC2 instance(s) should be launched (Example: subnet-17c1674a, subnet-2d5c8855, subnet-e0d425aa)
Set the ‘Token presented by https://acm.altinity.cloud’ with a token value from Step 2.
Important: At the last step of the wizard, checkmark the notice: “I acknowledge that AWS CloudFormation might create IAM resources with custom names”
Complete the wizard and submit the form.
EC2 background processing explained
The EC2 instance is processed in the background as follows:
In Altinity.Cloud
Select the ‘Proceed’ button in the connection wizard. NOTE: It is ok to select Proceed more than once, since provisioning takes some time. Once the EKS cluster is provisioned, wizard will switch to the ‘Resources Configuration’ page.
Finish configuration of node pools as described in the Resource Configuration section.
The AWS EC2 instance should meet the following requirements:
EC2 Instance Requirements
Set up a role with IAM policies to access IAM, EC2, VPC, EKS, S3 & Lambda as follows:
arn:aws:iam::aws:policy/IAMFullAccess
arn:aws:iam::aws:policy/AmazonEC2FullAccess
arn:aws:iam::aws:policy/AmazonVPCFullAccess
arn:aws:iam::aws:policy/AmazonS3FullAccess
arn:aws:iam::aws:policy/AWSLambda_FullAccess
arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore
NOTE:
AmazonSSMManagedInstanceCore
is used for the Break Glass Procedure over AWS SSM.{
"Version":"2012-10-17",
"Statement":[
{
"Effect":"Allow",
"Action":[
"eks :*"
],
"Resource":"*"
},
{
"Effect":"Allow",
"Action":"iam:PassRole",
"Resource":"*",
"Condition":{
"StringEquals":{
"iam:PassedToService":"eks.amazonaws.com"
}
}
}
]
}
To set this instance to have access to the EC2 metadata and Internet, set the Security group to:
Download altinitycloud-connect.
Run the installer using the following terminal command. NOTE: The following example is for an Intel Linux installation.
curl -sSL https://github.com/altinity/altinitycloud-connect/releases/download/v0.20.0/altinitycloud-connect-0.20.0-linux-amd64 -o altinitycloud-connect \
&& chmod a+x altinitycloud-connect \
&& sudo mv altinitycloud-connect /usr/local/bin/
Login to Altinity.Cloud and get a connection token.
NOTE: A cloud-connect.pem file is created in the current working directory.
altinitycloud-connect login --token=<registration token>
Connect to Altinity.Cloud:
altinitycloud-connect --capability aws
Start EKS provisioning
The following data is required in order to create the VPC and EKS cluster properly:
/21 recommended, e.g. 10.1.0.0/21)Please send this information to your Altinity support representative to start the EKS provisioning process. When completed, the Altinity Cloud Manager (ACM) will be updated then you can create your ClickHouse clusters.
The remainder of the provisioning process is handled by Altinity.Cloud. Users may switch back to ACM and wait for connection to be established in order to finish configuration.
In Altinity.Cloud
Select the Proceed button in the connection wizard. You may repeat this step more than once to see if the connection has completed, since provisioning takes some time. Once the EKS cluster is provisioned, the connection wizard will switch to the Resources Configuration page.
Finish the configuration of the node pools as described in the Resources Configuration section.
The “Break Glass” procedure allows Altinity access to EC2 instance with SSH, using AWS SSM in order to troubleshoot altinitycloud-connect that is running on this instance.
Create an AnywhereAdmin IAM role with trust policy set:
{
"Version":"2012-10-17",
"Statement":[
{
"Effect":"Allow",
"Principal":{
"AWS":"arn:aws:iam::313342380333:role/AnywhereAdmin"
},
"Action":"sts:AssumeRole"
}
]
}
Add a permission policy set:
{
"Version":"2012-10-17",
"Statement":[
{
"Effect":"Allow",
"Action":"ssm:StartSession",
"Resource":[
"arn:aws:ec2:$REGION:$ACCOUNT_ID:instance/$INSTANCE_ID",
"arn:aws:ssm:*:*:document/AWS-StartSSHSession"
]
}
]
}
Send the following ARN string to Altinity: NOTE: This is used to revoke the Break Glass Procedure access change, or remove the permission policy.
arn:aws:ec2:$REGION:$ACCOUNT_ID:instance/$INSTANCE_ID
8 May 2023 · Read time 1 min
This guide covers how to Altinity.Cloud Anywhere to install a Kubernetes ClickHouse environment on the Google Cloud Platform Google Kubernetes Engine (GKE).
This guide contains the following sections:
This page assume you have an Altinity.Cloud account and have requested an Anywhere environment, and have a developer Google Console environment set up.
Google Accounts
Altinity Accounts
Google API Permissions
In the Google Console, you must ENABLE the following SDKs for your project:
As a client computer (or cloud machine instance) is being used from the terminal to perform the installation instructions on this page, the following software items must first be installed and various configurations completed.
For the terminal
This section covers the setup and configuration of the Google command line software, configuration and how to create a Kubernetes container and GKE cluster.
8 May 2023 · Read time 5 min
This section covers the creation of a GKE Kubernetes container and cluster.
We start with this section with the assumption that you already have a Google Cloud account and know how to create a kubernetes environment. Included are links to installation sections that guide you through the process of installing the Google development environment. When you finish this section, you will be ready to use the Altinity Cloud Manager to provision and manage ClickHouse clusters.
Prerequisites Check that each of the items in the following list are complete:
gcloud version)kubectl config view)gcloud auth login)gcloud config list)Preparing your client computer for install Google GKE from the terminal includes the following sections:
After completing the preliminary setup, you are ready to set up an Altinity.Cloud ClickHouse connection to your Google environment:
The networks create command creates a GKE Kubernetes container that to host a cluster.
For more information, check out the following Google GKE documentation.
# Create Kubernetes 'kubernetes-1'
gcloud compute networks create kubernetes-1 \
--bgp-routing-mode regional \
--subnet-mode custom
Figure 1 - The command to create kubernetes-1 and Google’s response.
The clusters create command creates a GKE cluster inside the Google kubernetes container. Altinity then uses this cluster to set up ClickHouse when you use the Connection Setup wizard.
Use your browser to review the Google Kubernetes console to see the new cluster.
# Create Cluster 'cluster-1' inside Kubernetes 'kubernetes-1'
gcloud container clusters create cluster-1 \
--region us-west1 \
--node-locations us-west1-a,us-west1-b \
--machine-type n2-standard-4 \
--network kubernetes-1 \
--create-subnetwork name=k-subnet-1 \
--enable-ip-alias
Figure 2 - Running the clusters create command. The blue-highlighted items in the example screenshot are example values that you can alter by following Altinity recommendations.
The get-credentials command sets up your local config file so that kubectl commands are authorized to talk to the Google GKE.
Once the cluster is ready, use the following get-credentials command to allow kubectl to issue commands to Kubernetes. Highlighted in blue in the terminal screenshot is the name of the cluster cluster-1, the region us-west1, and the project name in this example any-test-gke.
NOTE: Figure 1 shows the project name as any-test-gke.
To authorize kubectl commands to access Google clusters:
Copy and paste the following command to your terminal:
gcloud container clusters get-credentials cluster-1 \
--region us-west1 \
--project my-project
Figure 3 - Running the Google get-credentials command so that kubectl commands are authorized to talk to the Google GKE environment.
After completing the preliminary setup, you are ready to set up an Altinity.Cloud ClickHouse connection to your Google environment:
8 May 2023 · Read time 3 min
For Linux Debian (Ubuntu) installations, install the following terminal commands on your client computer, entering the commands one at a time. For more details on each line, jump to the specific sections on this page:
# Certificates Install
sudo apt-get install apt-transport-https ca-certificates gnupg
echo "deb [signed-by=/usr/share/keyrings/cloud.google.gpg] https://packages.cloud.google.com/apt cloud-sdk main" | sudo tee -a /etc/apt/sources.list.d/google-cloud-sdk.list
# Install
curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key --keyring /usr/share/keyrings/cloud.google.gpg add –
sudo apt-get update && sudo apt-get install google-cloud-cli
sudo apt-get install google-cloud-sdk-gke-gcloud-auth-plugin
# Enable Services
gcloud services enable container.googleapis.com
This section includes example responses after each command.
Certificates are installed to validate the software is from a trusted source and allow the use of software repositories.
# Certificates Install 1
sudo apt-get install apt-transport-https ca-certificates gnupg
# Response
# ----------
# Reading package lists... Done
# Building dependency tree
# Reading state information... Done
# ca-certificates is already the newest version (20211016ubuntu0.20.04.1).
# gnupg is already the newest version (2.2.19-3ubuntu2.2).
# apt-transport-https is already the newest version (2.0.9).
# 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Add the gcloud CLI distribution URI as a package source to your local OS sources list. (Linux Debian example.)
# Certificates Install 2
echo "deb [signed-by=/usr/share/keyrings/cloud.google.gpg] \
https://packages.cloud.google.com/apt cloud-sdk main" | \
sudo tee -a /etc/apt/sources.list.d/google-cloud-sdk.list
# Response
# ----------
# deb [signed-by=/usr/share/keyrings/cloud.google.gpg] https://packages.cloud.google.com/apt cloud-sdk main
# ubuntu@ip-172-31-16-238:~$
Downloads the Google Cloud keyring and installs it to /usr/share/keyrings/cloud.google.gpg.
curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key --keyring /usr/share/keyrings/cloud.google.gpg add –
# Response
# ----------
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0gpg: can't open '–': No such file or directory
100 1210 100 1210 0 0 6205 0 --:--:-- --:--:-- --:--:-- 6237
(23) Failed writing body
ubuntu@ip-172-31-16-238:~$
Installs the Google Cloud API software.
curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key --keyring /usr/share/keyrings/cloud.google.gpg add –
# Response
# ----------
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0gpg: can't open '–': No such file or directory
100 1210 100 1210 0 0 5960 0 --:--:-- --:--:-- --:--:-- 5960
(23) Failed writing body
ubuntu@ip-172-31-16-238:~$ sudo apt-get update && sudo apt-get install google-cloud-cli
Hit:1 http://us-east-2.ec2.archive.ubuntu.com/ubuntu focal InRelease
Get:2 http://us-east-2.ec2.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:3 http://us-east-2.ec2.archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Hit:4 https://download.docker.com/linux/ubuntu bionic InRelease
Get:5 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Get:6 https://packages.cloud.google.com/apt cloud-sdk InRelease [6361 B]
Get:7 http://us-east-2.ec2.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [2534 kB]
Get:8 http://us-east-2.ec2.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1059 kB]
Get:9 http://us-east-2.ec2.archive.ubuntu.com/ubuntu focal-updates/universe amd64 c-n-f Metadata [24.2 kB]
Hit:10 https://packages.clickhouse.com/deb stable InRelease
Get:11 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [2151 kB]
Get:12 https://packages.cloud.google.com/apt cloud-sdk/main amd64 Packages [438 kB]
Get:13 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [834 kB]
Get:14 http://security.ubuntu.com/ubuntu focal-security/universe amd64 c-n-f Metadata [17.6 kB]
Fetched 7401 kB in 1s (5429 kB/s)
Reading package lists... Done
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:2
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:2
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:2
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:2
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:2
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:3
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:3
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:3
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:3
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:3
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:4
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:4
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:4
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:4
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:4
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:5
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:5
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:5
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:5
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:5
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:6
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:6
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:6
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:6
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:6
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:7
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:7
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:7
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:7
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:7
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:8
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:8
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:8
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:8
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:8
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:9
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:9
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:9
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:9
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:9
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:10
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:10
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:10
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:10
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:10
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:2
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:2
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:2
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:2
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:2
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:3
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:3
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:3
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:3
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:3
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:4
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:4
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:4
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:4
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:4
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:5
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:5
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:5
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:5
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:5
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:6
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:6
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:6
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:6
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:6
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:7
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:7
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:7
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:7
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:7
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:8
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:8
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:8
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:8
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:8
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:9
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:9
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:9
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:9
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:9
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:10
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:10
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:10
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:10
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:10
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
google-cloud-cli-app-engine-java google-cloud-cli-app-engine-python google-cloud-cli-pubsub-emulator google-cloud-cli-bigtable-emulator google-cloud-cli-datastore-emulator kubectl
The following packages will be upgraded:
google-cloud-cli
1 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
Need to get 154 MB of archives.
After this operation, 1508 kB disk space will be freed.
Get:1 https://packages.cloud.google.com/apt cloud-sdk/main amd64 google-cloud-cli all 430.0.0-0 [154 MB]
Fetched 154 MB in 3s (56.6 MB/s)
(Reading database ... 164975 files and directories currently installed.)
Preparing to unpack .../google-cloud-cli_430.0.0-0_all.deb ...
Unpacking google-cloud-cli (430.0.0-0) over (429.0.0-0) ...
Setting up google-cloud-cli (430.0.0-0) ...
Processing triggers for man-db (2.9.1-1) ...
ubuntu@ip-172-31-16-238:~$
Installs the Google auth plugin. Used to manage authentication between the Altinity client and the Google Kubernetes Engine.
sudo apt-get install google-cloud-sdk-gke-gcloud-auth-plugin
# Response
# ----------
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
google-cloud-sdk-gke-gcloud-auth-plugin
0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
Need to get 3129 kB of archives.
After this operation, 11.0 MB of additional disk space will be used.
Get:1 https://packages.cloud.google.com/apt cloud-sdk/main amd64 google-cloud-sdk-gke-gcloud-auth-plugin amd64 430.0.0-0 [3129 kB]
Fetched 3129 kB in 0s (7282 kB/s)
Selecting previously unselected package google-cloud-sdk-gke-gcloud-auth-plugin.
(Reading database ... 165046 files and directories currently installed.)
Preparing to unpack .../google-cloud-sdk-gke-gcloud-auth-plugin_430.0.0-0_amd64.deb ...
Unpacking google-cloud-sdk-gke-gcloud-auth-plugin (430.0.0-0) ...
dpkg: error processing archive /var/cache/apt/archives/google-cloud-sdk-gke-gcloud-auth-plugin_430.0.0-0_amd64.deb (--unpack):
trying to overwrite '/usr/lib/google-cloud-sdk/.install/gke-gcloud-auth-plugin.snapshot.json', which is also in package google-cloud-cli-gke-gcloud-auth-plugin 429.0.0-0
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/google-cloud-sdk-gke-gcloud-auth-plugin_430.0.0-0_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
ubuntu@ip-172-31-16-238:~$
Enables Google API services for your project.
gcloud services enable container.googleapis.com
# Response
# ----------
# none
8 May 2023 · Read time 1 min
For remote terminal installations, you need to login with your Google account. Use the same account you use to log into Google console.
Prerequisites
The workflow is:
gcloud config list command.To login to your Google account from a terminal:
Log in with your Google account using the command:
gcloud auth login
The resulting link URL that is displayed, copy and paste it to your browser.
Copy the authorization code string.
Return to the terminal, and at the Enter authorization code prompt, paste in the string as shown in the following terminal screenshot.
Check which account you are logged into with:
gcloud config list
Figure 1 - Log into your Google account using gcloud auth login command on your terminal.
8 May 2023 · Read time 1 min
The Google Project ID manages which environment to use for tracking and billing purposes. This must be set first before you begin the connection and provisioning process.
Check your Google Project ID From your Google console, choose your project ID from the menu in your web browser and check to make sure that is selected in the terminal as follows:
gcloud config get-value project
#example value
any-test-gke
If your Google Project ID is NOT listed, then list and set your Google project ID(s) by running:
gcloud projects list
# Example response
PROJECT_ID NAME PROJECT_NUMBER
any-test-gke any-test-gke 1234567890
# Set project ID example
gcloud config set project any-test-gke
The Altinity Cloud Manager includes a Connection Setup wizard that displays any time a new Environment is created that has not yet been connected. This section covers the use of the Connection Setup wizard, how to install the altinitycloud-connect command line software, and how to create a ClickHouse cluster and database.
8 May 2023 · Read time 4 min
This section shows you how to create a secure connection between your Google GKE environment and the Altinity Cloud Manager using the Altinity.Cloud Anywhere Connection Setup wizard on your web browser.
Prerequisites
Recommended
The Google Project ID manages which environment to use for tracking and billing purposes. This must be set first before you begin the connection and provisioning process.
Check your Google Project ID From your Google console, choose your project ID from the menu in your web browser and check to make sure that is selected in the terminal as follows:
gcloud config get-value project
#example value
any-test-gke
If your Google Project ID is NOT listed If your Google Project ID is NOT listed, then list and set your Google project ID(s) by running:
gcloud projects list
# Example response
PROJECT_ID NAME PROJECT_NUMBER
any-test-gke any-test-gke 1234567890
# Set project ID example
gcloud config set project any-test-gke
To verify you have altinitycloud-connect installed, run the following command:
altinitycloud-connect
# Example Response
0.20.0
# Installation location
where altinitycloud-connect
altinitycloud-connect is /usr/local/bin/altinitycloud-connect
In the Altinity Cloud Manager, the Connection Setup wizard is located in the Environments section of the ACM. This instruction assumes that you have either:
As shown in Figure 1, the Connection Setup wizard displays this screen when the selected environment (Example: gkeanywhere which is available from the top right Environment menu) is not yet a connection between the ACM and GKE.
The Connection Setup wizard provides 3 sections:
After that, you proceed to Creating a ClickHouse Cluster.
As indicated in Figure 1, step 1 directs you down download and install altinitycloud-connect. Binaries for various systems are provided.
From the Altinity Cloud Manager Connection Setup page, select the green PROCEED button.
From the same Altinity.Anywhere environment, copy the next string and paste it into your terminal. This begins the provisioning process on your Mac.
altinitycloud-connect kubernetes | kubectl apply -f -
Response The response appears similar to the following:
namespace/altinity-cloud-system created
namespace/altinity-cloud-managed-clickhouse created
clusterrole.rbac.authorization.k8s.io/altinity-cloud:node-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:node-metrics-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:storage-class-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:persistent-volume-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:cloud-connect unchanged
serviceaccount/cloud-connect created
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:cloud-connect unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:node-view unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:node-metrics-view unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:storage-class-view unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:persistent-volume-view unchanged
rolebinding.rbac.authorization.k8s.io/altinity-cloud:cloud-connect created
rolebinding.rbac.authorization.k8s.io/altinity-cloud:cloud-connect created
secret/cloud-connect created
deployment.apps/cloud-connect created
Confirm the following settings then select the green PROCEED button:
The tunneling daemon
Review the JSON data then select the green Finish button. Note: A message saying “Connection is not ready yet.” you can select “Continue waiting…” until the next screen appears.
Confirm the following settings then select the green FINISH button:
8 May 2023 · Read time 1 min
Altinity.Cloud Anywhere includes altinitycloud-connect, a tunneling daemon that creates a secure connection between Google GKE Kubernetes environmenet and the Altinity Cloud Manager.
Install altinitycloud-connect from the following links:
To verify you have altinitycloud-connect installed, run the following command:
altinitycloud-connect version
# Example Response
0.20.0
# Installation location
where altinitycloud-connect
altinitycloud-connect is /usr/local/bin/altinitycloud-connect
Running the altinitycloud-connect command with no parameters, displays the following options.
altinitycloud-connect
Usage:
cloud-connect [flags]
cloud-connect [command]
Available Commands:
completion Generate the autocompletion script for the specified shell
kubernetes Print Kubernetes manifest
kubernetes-disconnect Print Kubernetes disconnect manifest
login Log in
version Print version
Flags:
--ca-crt string /path/to/custom/ca.crt (defaults to $ALTINITY_CLOUD_CACERT)
--capability strings List of capabilities. Supported: aws, gcp, kubernetes (includes all by defaults)
--debug-addr string Address to serve /metrics & /healthz on (default ":0")
-i, --input string /path/to/cloud-connect.pem produced by login command (default "cloud-connect.pem")
-u, --url string URL to connect to (defaults to $ALTINITY_CLOUD_URL, and if not specified, to https://anywhere.altinity.cloud) (default "https://anywhere.altinity.cloud")
Use "cloud-connect [command] --help" for more information about a command.
7 May 2023 · Read time 2 min
These section covers how to use the Altinity Cloud Manager to create a ClickHouse cluster your your Google GKE Kubernetes environment.
To create a cluster (see Figure 1 for reference):
Use the The top left Environment menu to selects where your Google GKE environment is located. In this example as shown in Figure 1, the environment name is gkeanywhere.
Select Clusters from the navigation menu.
Select the LAUNCH CLUSTER blue button to launch the wizard.
The cluster panel is created, called test-gcp-anyw.
When the cluster has started, the status indicators shown in green will appear. These are nodes online and checks passed.
First time creating a cluster
If this is the first time you are viewing the Altinity Cloud Manager Clusters page, there will be no clusters, the screen will appear as in shown in Figure 2. The following steps lead you through the screens displayed by the Cluster Wizard. To create a new ClickHouse Cluster using the Launch Cluster wizard):
NOTE: Each of the 6 steps in the Wizard you can navigate back forth between the previously filled-in screens by selecting the title links on the left, or using the BACK and NEXT buttons.
To create a new ClickHouse cluster:
Your new ClickHouse Cluster will start building, and will complete with the green boxes under your cluster name test-gcp-anyw;
7 May 2023 · Read time 3 min
In this section you will create a ClickHouse database and tables on your Google GKE-cluster using the ACM. You will then use your cluster’s Explore menu in the ACM to run the database-creation scripts and queries. Finally, you will use the clickhouse-client command line tool from your local terminal using the Connection Details string to test data-retrieval queries.
The following steps you will use the clusters EXPLORE menu in the Query tab.
To create a new database on your Altinity.Cloud Anywhere cluster from the ACM:
CREATE TABLE IF NOT EXISTS events_local ON CLUSTER '{cluster}' (
event_date Date,
event_type Int32,
article_id Int32,
title String
) ENGINE = ReplicatedMergeTree('/clickhouse/{cluster}/tables/{shard}/{database}/{table}', '{replica}')
PARTITION BY toYYYYMM(event_date)
ORDER BY (event_type, article_id);
CREATE TABLE events ON CLUSTER '{cluster}' AS events_local
ENGINE = Distributed('{cluster}', default, events_local, rand())
INSERT INTO events VALUES(today(), 1, 13, 'Example');
SELECT * FROM events;
# Response
test-anywhere-6.johndoetest-a123.altinity.cloud:8443 (query time: 0.196s)
┌─event_date─┬─event_type─┬─article_id─┬─title───┐
│ 2023-03-24 │ 1 │ 13 │ Example │
└────────────┴────────────┴────────────┴─────────┘
show tables
# Response
test-anywhere-6.johndoetest-a123.altinity.cloud:8443 (query time: 0.275s)
┌─name─────────┐
│ events │
│ events_local │
└──────────────┘
This section shows you how to use your local computer terminal to login to your Clickhouse Cluster that you created in the Altinity Cloud Manager.
Prerequisite
Connection String
The connection string comes from your cluster (Example: test-gcp-anyw) Connection Details link. The Copy/Paste for client connections string highlighted in red in Figure 2 is used in your terminal (you supply the password; Example: adminpassword)
kubectl -n altinity-cloud-managed-clickhouse get all
# Response
NAME READY STATUS RESTARTS AGE
pod/chi-test-anywhere-6-johndoe-anywhere-6-0-0-0 2/2 Running 8 (3h25m ago) 2d17h
kubectl -n altinity-cloud-managed-clickhouse exec -it pod/chi-test-anywhere-6-johndoe-anywhere-6-0-0-0 -- bash
# Response
Defaulted container "clickhouse-pod" out of: clickhouse-pod, clickhouse-backup
clickhouse@chi-test-anywhere-6-johndoe-anywhere-6-0-0-0:/$
clickhouse@chi-test-anywhere-6-johndoe-anywhere-6-0-0-0:/$
clickhouse@chi-test-anywhere-6-johndoe-anywhere-6-0-0-0:/$ clickhouse-client
# Response
<jemalloc>: MADV_DONTNEED does not work (memset will be used instead)
<jemalloc>: (This is the expected behaviour if you are running under QEMU)
ClickHouse client version 22.8.13.21.altinitystable (altinity build).
Connecting to localhost:9000 as user default.
Connected to ClickHouse server version 22.8.13 revision 54460.
test-anywhere-6 :)
test-anywhere-6 :) show tables
# Response
SHOW TABLES
Query id: da01133d-0130-4b98-9090-4ebc6fa4b568
┌─name─────────┐
│ events │
│ events_local │
└──────────────┘
2 rows in set. Elapsed: 0.013 sec.
test-anywhere-6 :) SELECT * FROM events;
# Response
SELECT *
FROM events
Query id: 00fef876-e9b0-44b1-b768-9e662eda0483
┌─event_date─┬─event_type─┬─article_id─┬─title───┐
│ 2023-03-24 │ 1 │ 13 │ Example │
└────────────┴────────────┴────────────┴─────────┘
1 row in set. Elapsed: 0.023 sec.
test-anywhere-6 :)
Review the following database creation and query instructions:
4 May 2023 · Read time 2 min
The Google Console Home is where a NEW PROJECT is created.
The screenshot of the Google Console Welcome page is shown in Figure 1. Points of interest are marked in red.
A Google Project ID is first create in your Google Console. Create a Google Project with the NEW PROJECT button, and set up Billing.
Once you have a project name, you can select that in the terminal and complete the steps for creating a Kubernetes network and starting cluster that you will then connect to the Altinity.Cloud.
From the home page, when you select the Kubernetes Engine button, you will see a page that displays the cluster will be created from the terminal after following the instructions on this page.
From the home page, when you select the Compute Engine button, you will see a page that displays all the nodes created from the terminal. The names matches what you see in the k9s monitoring windows that view the Altinity and ClickHouse Kubernetes namespaces.
8 May 2023 · Read time 8 min
To use gcloud to install kubectl according to the Google GKE instructions:
gcloud components install kubectl
sudo apt-get install kubectl
Use curl to install kubectl according to the Kubernetes website:
curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
sudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl
This is an expanded listing using the cluster info command (many hundreds of lines).
kubectl cluster-info dump
# Example response for a very long cluster information dump
# -----------------------------------------------------------
# {
# "kind": "NodeList",
# "apiVersion": "v1",
# "metadata": {
# "resourceVersion": "8685921"
# },
# "items": [
# {
# "metadata": {
# "name": "gke-cluster-1-default-pool-36e9706c-0fxb",
# "uid": "0b89edcc-d46b-4783-84f9-a7672f0bd922",
# ...
# ... several hundred lines
# ...
# 13. __clone @ 0x122293 in /usr/lib/x86_64-linux-gnu/libc-2.31.so
# (version 21.8.10.1.altinitystable (altinity build))
# 2023.04.14 06:24:31.919921 [ 115 ] {} <Debug> DNSResolver: Updated DNS cache
# 2023.04.14 06:24:35.915268 [ 54 ] {} <Debug> DiskLocal: Reserving 1.00 MiB on disk `default`, having unreserved 97.44 GiB.
# ==== END logs for container clickhouse of pod default/chi-first-first-1-1-0 ====
To enter the pod and run the ClickHouse client directly, first locate the nodename of the cluster using the watch or k9s or find it from the ACM.
kubectl exec -it chi-first-first-0-0-0 -- bash
# You are now inside the pod, run a list command:
root@chi-first-first-0-0-0:/# ls
## bin boot cloud-connect.pem dev docker-entrypoint-initdb.d entrypoint.sh etc home kubectl kubectl.sha256 lib lib32 lib64 libx32 media mnt opt proc root run sbin srv sys tmp usr var
# To exit out of the pod
exit
# ubuntu@ip-123-45-67-890:~$
This lists the currently registered Kubernetes namespaces in the current cluster-1 using the kubectl get ns command.
kubectl get ns command to list all of the namespaces.
List the CPU pods in a ClickHouse cluster.
kubectl get pod -o=custom-columns=NAME:.metadata.name,STATUS:.status.phase,NODE:.spec.nodeName
# Example response to list pods
# ------------------------------
# NAME STATUS NODE
# chi-first-first-0-0-0 Running gke-cluster-1-default-pool-36e9706c-xj7p
# chi-first-first-0-1-0 Running gke-cluster-1-default-pool-aa3988ca-nth7
# chi-first-first-1-0-0 Running gke-cluster-1-default-pool-36e9706c-0fxb
# chi-first-first-1-1-0 Running gke-cluster-1-default-pool-36e9706c-wrbm
List the storage volumes.
kubectl get pvc
# Example response to list volumes
# --------------------------------
# NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
# pd-ssd-chi-first-first-0-0-0 Bound pvc-5bc72a03-2ae5-41d1-9e93-92b92829c435 100Gi RWO premium-rwo 8d
# pd-ssd-chi-first-first-0-1-0 Bound pvc-ec8f143d-c51d-4125-938a-76ad103fb7f2 100Gi RWO premium-rwo 8d
# pd-ssd-chi-first-first-1-0-0 Bound pvc-014d010b-d282-4b47-91ef-b332bd381a28 100Gi RWO premium-rwo 8d
# pd-ssd-chi-first-first-1-1-0 Bound pvc-c11d5819-1935-4b6f-ad54-60fa196fe013 100Gi RWO premium-rwo 8d
To list the Zookeeper nodes:
kubectl get all -n zoo1ns
# Example response to list zookeeper nodes and services
# -----------------------------------------------------
# NAME READY STATUS RESTARTS AGE
# pod/zookeeper-0 1/1 Running 0 8d
#
# NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
# service/zookeeper ClusterIP 10.72.131.73 <none> 2181/TCP,7000/TCP 8d
# service/zookeepers ClusterIP None <none> 2888/TCP,3888/TCP 8d
#
# NAME READY AGE
# statefulset.apps/zookeeper 1/1 8d
List Storage Classes. (See ACM 》 Resources Configuration 》 Storage Classes )
kubectl describe storageclass
# Example response to list all the storage
# ----------------------------------------
# Name: premium-rwo
# IsDefaultClass: No
# Annotations: components.gke.io/component-name=pdcsi,components.gke.io/component-version=0.13.7,components.gke.# io/layer=addon
# Provisioner: pd.csi.storage.gke.io
# Parameters: type=pd-ssd
# AllowVolumeExpansion: True
# MountOptions: <none>
# ReclaimPolicy: Delete
# VolumeBindingMode: WaitForFirstConsumer
# Events: <none>
#
#
# Name: standard
# IsDefaultClass: No
# Annotations: components.gke.io/layer=addon,storageclass.kubernetes.io/is-default-class=false
# Provisioner: kubernetes.io/gce-pd
# Parameters: type=pd-standard
# AllowVolumeExpansion: True
# MountOptions: <none>
# ReclaimPolicy: Delete
# VolumeBindingMode: Immediate
# Events: <none>
#
#
# Name: standard-rwo
# IsDefaultClass: Yes
# Annotations: components.gke.io/layer=addon,storageclass.kubernetes.io/is-default-class=true
# Provisioner: pd.csi.storage.gke.io
# Parameters: type=pd-balanced
# AllowVolumeExpansion: True
# MountOptions: <none>
# ReclaimPolicy: Delete
# VolumeBindingMode: WaitForFirstConsumer
# Events: <none>
To verify the config file is updated with the correct credentials, review it by running the kubctl config view command.
kubctl config view.svg command to verify that the config file is updated with credentials.
This lists the current container information with the gcloud container clusters list command.
gcloud container clusters list command.
Run the kubectl clusterinfo command to list the Kubernetes control plan and services.
At this point the Google set up is complete.
Now you can use Altinity.Cloud Anywhere to connect Google GKE to the Altinity Cloud Manager.
kubectl clusterinfo command.
The computer or cloud compute instance that you use to communicate with Google Cloud requires installation of the Google CLI and Kubernetes.
The following list of software needs to be installed:
kubectl get namespaces)version checks that some items you do not have
Checking Versions To make sure the prerequisites have been met, check the versions of the installed software.
# Version checks
kubectl version --short # v1.27.1
cat /etc/os-release # Ubuntu 20.04
altinitycloud-connect version # Altinity 0.20.0
gcloud version # Google Cloud SDK 429.0.0
kubectl version --short
# Client Version: v1.26.3
# Kustomize Version: v4.5.7
# Unable to connect to the server: net/http: TLS handshake timeout
# Another variation to display version
kubectl version --output=yaml
8 May 2023 · Read time 1 min
To to terminal software installations, you will need to know what operating system is being used so you can choose the correct binaries.
In the Google CLI console, Check the OS Version
cat /etc/os-release
# Response from Google console
-----------
# PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
# NAME="Debian GNU/Linux"
# VERSION_ID="11"
# VERSION="11 (bullseye)"
# VERSION_CODENAME=bullseye
# ID=debian
# HOME_URL="https://www.debian.org/"
# SUPPORT_URL="https://www.debian.org/support"
# BUG_REPORT_URL="https://bugs.debian.org/"
# Response from Ubuntu SSH Terminal
-----------
# PRETTY_NAME="Ubuntu 22.04.2 LTS"
# NAME="Ubuntu"
# VERSION_ID="22.04"
# VERSION="22.04.2 LTS (Jammy Jellyfish)"
# VERSION_CODENAME=jammy
# ID=ubuntu
# ID_LIKE=debian
# HOME_URL="https://www.ubuntu.com/"
# SUPPORT_URL="https://help.ubuntu.com/"
# BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
# PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
# UBUNTU_CODENAME=jammy
Displays Kubernetes roles and resources that the kubect apply will use run the following command and save the output from your terminal as a text file to read.
altinitycloud-connect kubernetes
# Response example
---------------
# apiVersion: v1
# kind: Namespace
# metadata:
# name: altinity-cloud-system
# ---
# apiVersion: v1
# kind: Namespace
# metadata:
# name: altinity-cloud-managed-clickhouse
# ---
# apiVersion: rbac.authorization.k8s.io/v1
# kind: ClusterRole
#
# ... several more lines
#
# name: cloud-connect
# volumeMounts:
# - mountPath: /etc/cloud-connect
# name: secret
# serviceAccountName: cloud-connect
# volumes:
# - name: secret
# secret:
# secretName: cloud-connect
Use a watch command when you want to monitor node activity of the altinity-cloud namespaces in real time. This is useful for installations that are taking a long time, and you wish to watch the provisioning process.
Run the watch commands on the two altinity-cloud prefixed namespaces using the following commands:
watch -n altinity-cloud-system get all
watch -n altinity-cloud-managed-clickhouse get all
watch kubectl -n altinity-cloud-system get all
# Example response
# ---------------------------
Every 2.0s: kubectl -n altinity-cloud-system get all john.doe-MacBook-Pro.local: Sun Mar 19 23:03:18 2023
NAME READY STATUS RESTARTS AGE
pod/cloud-connect-d6ff8499f-bkc5k 1/1 Running 0 10h
pod/crtd-665fd5cb85-wqkkk 1/1 Running 0 10h
pod/edge-proxy-66d44f7465-t9446 2/2 Running 0 10h
pod/grafana-5b466574d-vvt9p 1/1 Running 0 10h
pod/kube-state-metrics-58d86c747c-7hj79 1/1 Running 0 10h
pod/node-exporter-762b5 1/1 Running 0 10h
pod/prometheus-0 1/1 Running 0 10h
pod/statuscheck-f7c9b4d98-2jlt6 1/1 Running 0 10h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/edge-proxy ClusterIP 10.109.2.17 <none> 443/TCP,8443/TCP,9440/TCP 10h
service/edge-proxy-lb LoadBalancer 10.100.216.192 <pending> 443:31873/TCP,8443:32612/TCP,9440:31596/TCP 10h
service/grafana ClusterIP 10.108.24.91 <none> 3000/TCP 10h
service/prometheus ClusterIP 10.102.103.141 <none> 9090/TCP 10h
service/prometheus-headless ClusterIP None <none> 9090/TCP 10h
service/statuscheck ClusterIP 10.101.224.247 <none> 80/TCP 10h
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/node-exporter 1 1 1 1 1 <none> 10h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/cloud-connect 1/1 1 1 10h
deployment.apps/crtd 1/1 1 1 10h
deployment.apps/edge-proxy 1/1 1 1 10h
deployment.apps/grafana 1/1 1 1 10h
deployment.apps/kube-state-metrics 1/1 1 1 10h
deployment.apps/statuscheck 1/1 1 1 10h
NAME DESIRED CURRENT READY AGE
replicaset.apps/cloud-connect-d6ff8499f 1 1 1 10h
replicaset.apps/crtd-665fd5cb85 1 1 1 10h
replicaset.apps/edge-proxy-66d44f7465 1 1 1 10h
replicaset.apps/grafana-5b466574d 1 1 1 10h
replicaset.apps/grafana-6478f89b7c 0 0 0 10h
replicaset.apps/kube-state-metrics-58d86c747c 1 1 1 10h
replicaset.apps/statuscheck-f7c9b4d98 1 1 1 10h
NAME READY AGE
statefulset.apps/prometheus 1/1 10h
Figure 1 - The watch monitoring window for the namespaces altinity-cloud-system listing each node name, IP address, and the run status.
watch kubectl -n altinity-cloud-managed-clickhouse get all
# Example response
# ---------------------------
Every 2.0s: kubectl -n altinity-cloud-managed-clickhouse get all john.doe-MacBook-Pro.local: Mon Mar 20 00:14:44 2023
NAME READY STATUS RESTARTS AGE
pod/chi-test-anywhere-6-test-anywhere-6-0-0-0 2/2 Running 0 11h
pod/clickhouse-operator-996785fc-rgfvl 2/2 Running 0 11h
pod/zookeeper-5244-0 1/1 Running 0 11h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/chi-test-anywhere-6-test-anywhere-6-0-0 ClusterIP 10.98.202.85 <none> 8123/TCP,9000/TCP,9009/TCP 11h
service/clickhouse-operator-metrics ClusterIP 10.109.90.202 <none> 8888/TCP 11h
service/clickhouse-test-anywhere-6 ClusterIP 10.100.48.57 <none> 8443/TCP,9440/TCP 11h
service/zookeeper-5244 ClusterIP 10.101.71.82 <none> 2181/TCP,7000/TCP 11h
service/zookeepers-5244 ClusterIP None <none> 2888/TCP,3888/TCP 11h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/clickhouse-operator 1/1 1 1 11h
NAME DESIRED CURRENT READY AGE
replicaset.apps/clickhouse-operator-996785fc 1 1 1 11h
NAME READY AGE
statefulset.apps/chi-test-anywhere-6-test-anywhere-6-0-0 1/1 11h
statefulset.apps/zookeeper-5244 1/1 11h
Figure 2 - The watch monitoring window for the namespace altinity-cloud-managed-clickhouse, listing each node name, IP address, and the run status.
K9s is similar to the watch command for monitoring nodes in real time, but displayed in color and in a smaller interactive window, K9S is a free utility that lets you monitor in real time the progress of a provisioning installation.
To open monitoring windows for each altinity-cloud namespaces, open a new terminal instance and run the k9s command:
k9s -n altinity-cloud-system
k9s -n altinity-cloud-managed-clickhouse
8 May 2023 · Read time 4 min
This section lists adminstration tasks to:
To see detail instructions with screenshots to rescale your GKE cluster using the Altinity Cloud Manager cluster tools, follow the instructions on this page:
Use the Altinity Cloud Manager menu in your cluster: Actions 》Rescale to change:
To rescale your GKE cluster using the Altinity Cloud Manager cluster tools:
Resetting your Altinity.Cloud anywhere ClickHouse cluster from the ACM and your GKE environment will let you create a new connection.
In the Environment section, selecting your Anywhere environment name displays the Connection Setup wizard.
use the ACM Reset Anywhere function, then run the terminal commands to delete the ClickHouse
The result is that you will see the Anywhere Connection Setup screen and provisioning wizard that shows you the connection string to copy and paste to deploy a new Anywhere environment.
This section covers how to delete your GKE cluster using the ACM’s Reset Anywhere function, then removing the altinity-cloud namespaces from your GKE environment.
Check your namespaces to confirm that the altinity-cloud namespaces are present.
kubectl get ns
NAME STATUS AGE
altinity-cloud-managed-clickhouse Active 12d
altinity-cloud-system Active 12d
default Active 12d
kube-node-lease Active 12d
kube-public Active 12d
kube-system Active 12d
To delete ClickHouse services and altinity-cloud namespaces, run the following commands in sequence:
kubectl delete chi --all -n altinity-cloud-managed-clickhouse
kubectl delete ns altinity-cloud-managed-clickhouse
kubectl delete ns altinity-cloud-system
Check the namespace to verify the two with the prefix altinity-cloud are deleted.
kubectl get ns
NAME STATUS AGE
default Active 12d
kube-node-lease Active 12d
kube-public Active 12d
kube-system Active 12d
More Information
From your glcoud terminal, delete your GKE cluster as follows:
gcloud container clusters list
cluster-1 us-west1 1.24.10-gke.2300 35.230.115.228 n2-standard-4 1.24.10-gke.2300 6 RUNNING
gcloud container clusters delete cluster-1 --zone=us-west1
More Information
type: post keywords:
This page shows how the Altinity Cloud Manager with an Altinity.Anywhere installation to remotely rescale a customer’s on-prem cluster.
Select a cluster, then use the Actions > Rescale menu to bring up the Rescale Cluster window, then in the Desired Cluster Size, change the Number of Shards from 1 to 2 then press OK, then CONFIRM.
The Ubuntu host the Kubernetes installation is installed on shows the various commmands use to verify the changes made from the ACM.
The nodes online pill box will show grey, 2/4 nodes online, then after several minutes, turn green showing 4/4 nodes online. If you do not see the grey 2/4 nodes online, and the nodes online is green and shows 2/2 nodes online, try the rescale operation again.
Use the command kubectl -n altinity-cloud-managed-clickhouse... showing the Altinity clusters before the rescale operation.
kubectl -n <Altinity cluster name> running on-prem, that is managed from also by the ACM.
Ubuntu command kubectl get nodes before the rescale operation.
kubectl get nodes shows all the nodes on the Altinity ClickHouse cluster.
The newly spun up shard in cluster-x now reads 4/4 nodes online.
24 April 2023 · Read time 30 min
This guide covers the installation of Minikube in your own Kubernetes environment by using Altinity.Cloud Anywhere to do the provisioning. Any computer or cloud instance that can run Kubernetes and Minikube will work. Note that while Minicube is ok to use for development purposes, it should not be used for production.
These instructions have been tested on:
The following Altinity.Cloud service subscriptions are needed:
Server requirements
Minikube needs a minimum of 2 processors. Allocate RAM and disk space to accommodate your clusters. Check the values by running the terminal commands (Example: lscpu).
lscpu, or sysctl -a [for Mac])grep MemTotal /proc/meminfo )df -h)The following software must first be installed on your Minikube installation:
The following software is installed as part of the provisioning:
From a terminal, check the versions of all the installed software by running each command in turn.
Checking versions To make sure you have the required software installed, check the versions for each using the following commands:
docker --version
docker-machine --version
docker-compose --version
minikube version
kubectl version -o json
watch --version
k9s version
altinitycloud-connect version
From the terminal, run the command:
minikube start
Linux ARM Ubuntu 22.04 This is Minikube’s response from an Ubuntu 22.04 server running on ARM:
# minikube start
😄 minikube v1.30.1 on Ubuntu 22.04 (arm64)
✨ Using the qemu2 driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🔄 Restarting existing qemu2 VM for "minikube" ...
🐳 Preparing Kubernetes v1.26.3 on Docker 20.10.23 ...
🔗 Configuring bridge CNI (Container Networking Interface) ...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🔎 Verifying Kubernetes components...
🌟 Enabled addons: default-storageclass, storage-provisioner
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
Linux ARM Apple Macintosh M1 This is Minikube’s response from a Mac running Ventura:
# minikube start
😄 minikube v1.29.0 on Darwin 13.2.1 (arm64)
✨ Using the docker driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🚜 Pulling base image ...
🏃 Updating the running docker "minikube" container ...
🐳 Preparing Kubernetes v1.26.1 on Docker 20.10.23 ...
🔗 Configuring bridge CNI (Container Networking Interface) ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟 Enabled addons: storage-provisioner, default-storageclass
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
Linux Windows Intel This is Minikube’s response from a Microsoft Windows system running Ubuntu:
# minikube start
😄 minikube v1.30.1 on Ubuntu 20.04
✨ Using the docker driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🚜 Pulling base image ...
🔄 Restarting existing docker container for "minikube" ...
🐳 Preparing Kubernetes v1.26.3 on Docker 23.0.2 ...
🔗 Configuring bridge CNI (Container Networking Interface) ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟 Enabled addons: storage-provisioner, default-storageclass
🏄 Done! kubectl is now configured to use "minikube" cluster and "default"
Checking Minikube’s status If you are not sure if Minikube is already running, run a status check as follows:
minikube status
# minikube
# type: Control Plane
# host: Running
# kubelet: Running
# apiserver: Running
# kubeconfig: Configured
Checking the Kubernetes kubectl command This step checks that the kubectl command works on your Minikube host. Running the kubectl get ns command lists the namespaces that are currently running on your Minikube server.
Run the kubectl namespace list command:
kubectl get ns
# Example response:
# -------------------
# NAME STATUS AGE
# default Active 15d
# kube-node-lease Active 15d
# kube-public Active 15d
# kube-system Active 15d
To start the Connection Setup:
From the Altinity Cloud Manager, select the Environments section, then make sure you are in the correct environment by selecting it from the menu located at the top right of the screen.
In Figure 1 the Connection Setup step 2, Connect to Altinity.Cloud text box, select all the text.
In your Minikube terminal, copy and paste the text and press the return key. A command prompt appears immediately.
altinitycloud-connect login --token=
eyJhbGciOiJSUzI1Ni 808 characters Rpbml0eS5jbG91ZCIsImV4cCI6MTY3
OTMzNzMwMywic3ViIjoicm1rYzIzdGVzdC1kNDgxIn0.tODyYF8WnTSx6mbAZA5uwW176... cont.
Example altinitycloud-connect login token string from the Altinity Cloud Manager Connection Setup wizard step 2, Connect to Altinity.Cloud.
From Figure 1, in the Connection Setup screen step 3, Deploy connector to your Kubernetes cluster, copy the string and paste it into your terminal. This begins the provisioning process inside your Minikube Kubernetes environment.
altinitycloud-connect kubernetes | kubectl apply -f -
Response The response appears similar to the following:
namespace/altinity-cloud-system created
namespace/altinity-cloud-managed-clickhouse created
clusterrole.rbac.authorization.k8s.io/altinity-cloud:node-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:node-metrics-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:storage-class-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:persistent-volume-view unchanged
clusterrole.rbac.authorization.k8s.io/altinity-cloud:cloud-connect unchanged
serviceaccount/cloud-connect created
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:cloud-connect unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:node-view unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:node-metrics-view unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:storage-class-view unchanged
clusterrolebinding.rbac.authorization.k8s.io/altinity-cloud:persistent-volume-view unchanged
rolebinding.rbac.authorization.k8s.io/altinity-cloud:cloud-connect created
rolebinding.rbac.authorization.k8s.io/altinity-cloud:cloud-connect created
secret/cloud-connect created
deployment.apps/cloud-connect created
From the Altinity Cloud Manager Connection Setup page, select the green PROCEED button.
Confirm the following settings, then select the green PROCEED button:
NOTE: In Figure 2, if the table for the Node Pools section does not include a row for your Minikube server, select the ADD NODE POOL button and add the Zone name and Instance Type name and Capacity, and check each of the Used For checkboxes as shown.
In Figure 3, the Confirmation tab displays the Resources Specifications text box. Review these values and correct them if necessary by selecting the Resources Configuration tab to make changes.
To complete the Connection Setup wizard:
Select the green Finish button.
Select “Continue waiting…” until the next screen appears.
In the Confirmation screen shown in Figure 3, an example Resources Specification JSON string appears with the names of the storageClasses, nodePools and instanceType, zone and capacity value.
{
"storageClasses": [
{
"name": "standard"
}
],
"nodePools": [
{
"for": [
"CLICKHOUSE",
"ZOOKEEPER",
"SYSTEM"
],
"instanceType" : "minikube-node",
"zone" : "minikube-zone-a",
"capacity" : 10
}
]
}
The following step registers your Minikube label so that the ACM can find your ClickHouse Kubernetes server that Altinity.Cloud just provisioned for you. Refer to the Resource Specification JSON for the values for instanceType minikube-node and zone name minikube-zone-a where they are set.
Run the following string from your Kubernetes host terminal.
kubectl --context=minikube label nodes minikube \
node.kubernetes.io/instance-type=minikube-node \
topology.kubernetes.io/zone=minikube-zone-a
To monitor in real time the progress of a provisioning installation, run the watch commands on the two altinity-cloud prefixed namespaces.
Running Watch command 1 of 2 To monitor the process of the provisioning, use the watch or k9s command utility to monitor altinity-cloud-system. The display updates every 2 seconds.
watch kubectl -n altinity-cloud-system get all
Response The result appears similar to the following display:
Every 2.0s: kubectl -n altinity-cloud-system get all john.doe-yourcomputer.local: Sun Mar 19 23:03:18 2023
NAME READY STATUS RESTARTS AGE
pod/cloud-connect-d6ff8499f-bkc5k 1/1 Running 0 10h
pod/crtd-665fd5cb85-wqkkk 1/1 Running 0 10h
pod/edge-proxy-66d44f7465-t9446 2/2 Running 0 10h
pod/grafana-5b466574d-vvt9p 1/1 Running 0 10h
pod/kube-state-metrics-58d86c747c-7hj79 1/1 Running 0 10h
pod/node-exporter-762b5 1/1 Running 0 10h
pod/prometheus-0 1/1 Running 0 10h
pod/statuscheck-f7c9b4d98-2jlt6 1/1 Running 0 10h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/edge-proxy ClusterIP 10.109.2.17 <none> 443/TCP,8443/TCP,9440/TCP 10h
service/edge-proxy-lb LoadBalancer 10.100.216.192 <pending> 443:31873/TCP,8443:32612/TCP,9440:31596/TCP 10h
service/grafana ClusterIP 10.108.24.91 <none> 3000/TCP 10h
service/prometheus ClusterIP 10.102.103.141 <none> 9090/TCP 10h
service/prometheus-headless ClusterIP None <none> 9090/TCP 10h
service/statuscheck ClusterIP 10.101.224.247 <none> 80/TCP 10h
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/node-exporter 1 1 1 1 1 <none> 10h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/cloud-connect 1/1 1 1 10h
deployment.apps/crtd 1/1 1 1 10h
deployment.apps/edge-proxy 1/1 1 1 10h
deployment.apps/grafana 1/1 1 1 10h
deployment.apps/kube-state-metrics 1/1 1 1 10h
deployment.apps/statuscheck 1/1 1 1 10h
NAME DESIRED CURRENT READY AGE
replicaset.apps/cloud-connect-d6ff8499f 1 1 1 10h
replicaset.apps/crtd-665fd5cb85 1 1 1 10h
replicaset.apps/edge-proxy-66d44f7465 1 1 1 10h
replicaset.apps/grafana-5b466574d 1 1 1 10h
replicaset.apps/grafana-6478f89b7c 0 0 0 10h
replicaset.apps/kube-state-metrics-58d86c747c 1 1 1 10h
replicaset.apps/statuscheck-f7c9b4d98 1 1 1 10h
NAME READY AGE
statefulset.apps/prometheus 1/1 10h
Running Watch command 2 of 2 Open a second terminal window to monitor altinity-cloud-managed-clickhouse.
watch kubectl -n altinity-cloud-system get all
Response The result appears similar to the following display:
Every 2.0s: kubectl -n altinity-cloud-managed-clickhouse get all john.doe-yourcomputer.local: Mon Mar 20 00:14:44 2023
NAME READY STATUS RESTARTS AGE
pod/chi-test-anywhere-6-test-anywhere-6-0-0-0 2/2 Running 0 11h
pod/clickhouse-operator-996785fc-rgfvl 2/2 Running 0 11h
pod/zookeeper-5244-0 1/1 Running 0 11h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/chi-test-anywhere-6-test-anywhere-6-0-0 ClusterIP 10.98.202.85 <none> 8123/TCP,9000/TCP,9009/TCP 11h
service/clickhouse-operator-metrics ClusterIP 10.109.90.202 <none> 8888/TCP 11h
service/clickhouse-test-anywhere-6 ClusterIP 10.100.48.57 <none> 8443/TCP,9440/TCP 11h
service/zookeeper-5244 ClusterIP 10.101.71.82 <none> 2181/TCP,7000/TCP 11h
service/zookeepers-5244 ClusterIP None <none> 2888/TCP,3888/TCP 11h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/clickhouse-operator 1/1 1 1 11h
NAME DESIRED CURRENT READY AGE
replicaset.apps/clickhouse-operator-996785fc 1 1 1 11h
NAME READY AGE
statefulset.apps/chi-test-anywhere-6-test-anywhere-6-0-0 1/1 11h
statefulset.apps/zookeeper-5244 1/1 11h
Similar to Watch, but in color and in a smaller interactive window, K9S is a free utility that lets you monitor in real time the progress of a provisioning installation.
To open monitoring windows for each altinity-cloud namespaces, open a new terminal instance and run the k9s command:
k9s -n altinity-cloud-system
k9s -n altinity-cloud-managed-clickhouse
KS9 monitoring terminal windows
When provisioning is complete and the connection is established, the ACM displays the dashboard page showing the green connected icon. Since there is no cluster yet, the dashboard shows zeros for the number of Nodes and Clusters.
To verify the presence of the new namespaces on your Minikube server, open a third terminal window and list the namespaces to show the two altinity-cloud additions:
kubectl get ns
Response Note the two new altinity-cloud namespaces at the top:
NAME STATUS AGE
altinity-cloud-managed-clickhouse Active 8h
altinity-cloud-system Active 8h
default Active 16d
kube-node-lease Active 16d
kube-public Active 16d
kube-system Active 16d
These instructions run through the use of the Altinity.Cloud Manager (ACM) Clusters > LAUNCH CLUSTER wizard to create a ClickHouse cluster running in a Minikube Kubernetes environment. The Cluster dashboard in Figure 6 shows the finished result.
To create a new ClickHouse Cluster using the Launch Cluster wizard:
NOTE: The Cluster Launch Wizard lets you navigate back and forth between the previously filled-in screens by selecting the title links on the left, or using the BACK and NEXT buttons.
Your new ClickHouse Cluster will start building inside your Minikube. When the cluster is finished building and running, the cluster dashboard appears, similar to the screenshot shown in Figure 6. Beside your cluster name, two green status boxes nodes online, and checks passed appear.
In this section, you will create tables on your cluster using the ACM and run queries from both the ACM and then from your local terminal.
To create a new database on your Altinity.Cloud Anywhere cluster from the ACM:
CREATE TABLE IF NOT EXISTS events_local ON CLUSTER '{cluster}' (
event_date Date,
event_type Int32,
article_id Int32,
title String
) ENGINE = ReplicatedMergeTree('/clickhouse/{cluster}/tables/{shard}/{database}/{table}', '{replica}')
PARTITION BY toYYYYMM(event_date)
ORDER BY (event_type, article_id);
CREATE TABLE events ON CLUSTER '{cluster}' AS events_local
ENGINE = Distributed('{cluster}', default, events_local, rand())
INSERT INTO events VALUES(today(), 1, 13, 'Example');
SELECT * FROM events;
# Response
test-anywhere-6.johndoetest-a123.altinity.cloud:8443 (query time: 0.196s)
┌─event_date─┬─event_type─┬─article_id─┬─title───┐
│ 2023-03-24 │ 1 │ 13 │ Example │
└────────────┴────────────┴────────────┴─────────┘
show tables
# Response
test-anywhere-6.johndoetest-a123.altinity.cloud:8443 (query time: 0.275s)
┌─name─────────┐
│ events │
│ events_local │
└──────────────┘
This section shows you how to use your local Minikube computer terminal to log into your Clickhouse Cluster that ACM created. NOTE: With Minikube, you cannot use your cluster Connection Details strings to directly run clickhouse-client commands, you must first log into the ClickHouse pod as described in the following steps.
kubectl -n altinity-cloud-managed-clickhouse get all
# Response
NAME READY STATUS RESTARTS AGE
pod/chi-test-anywhere-6-johndoe-anywhere-6-0-0-0 2/2 Running 8 (3h25m ago) 2d17h
kubectl -n altinity-cloud-managed-clickhouse exec -it pod/chi-test-anywhere-6-johndoe-anywhere-6-0-0-0 -- bash
# Response
Defaulted container "clickhouse-pod" out of: clickhouse-pod, clickhouse-backup
clickhouse@chi-test-anywhere-6-johndoe-anywhere-6-0-0-0:/$
clickhouse@chi-test-anywhere-6-johndoe-anywhere-6-0-0-0:/$
clickhouse@chi-test-anywhere-6-johndoe-anywhere-6-0-0-0:/$ clickhouse-client
# Response
<jemalloc>: MADV_DONTNEED does not work (memset will be used instead)
<jemalloc>: (This is the expected behavior if you are running under QEMU)
ClickHouse client version 22.8.13.21.altinitystable (altinity build).
Connecting to localhost:9000 as user default.
Connected to ClickHouse server version 22.8.13 revision 54460.
test-anywhere-6 :)
test-anywhere-6 :) show tables
# Response
SHOW TABLES
Query id: da01133d-0130-4b98-9090-4ebc6fa4b568
┌─name─────────┐
│ events │
│ events_local │
└──────────────┘
2 rows in set. Elapsed: 0.013 sec.
test-anywhere-6 :) SELECT * FROM events;
# Response
SELECT *
FROM events
Query id: 00fef876-e9b0-44b1-b768-9e662eda0483
┌─event_date─┬─event_type─┬─article_id─┬─title───┐
│ 2023-03-24 │ 1 │ 13 │ Example │
└────────────┴────────────┴────────────┴─────────┘
1 row in set. Elapsed: 0.023 sec.
test-anywhere-6 :)
Exiting from ClickHouse client and your pod
exit command.exit command again.pwd (print working directory) to see what directory you are currently in.aws-anyw-test :) exit
Bye.
clickhouse@chi-was-anyw-test-was-anyw-test-0-0-0:/$ exit
exit
ubuntu@ip-172-31-16-238:~$
ubuntu@ip-172-31-16-238:~$ pwd
/home/ubuntu
Review the following database creation and query instructions:
This section provides a few commonly used Minikube maintenance operations.
Use the Altinity Cloud Manager Actions 》Rescale to change the CPU, Node Storage, Volumes, and Number of Shards and Replicas.
Note that cluster Node Storage size may not be decreased, only increased by at least 10%.
Reset your Altinity.Cloud Anywhere cluster from the ACM and your Minikube installation to create a new Altinity.Cloud Anywhere connection.
To use the Reset Anywhere function.
The result is that you will see the Anywhere Connection Setup screen and provisioning wizard that shows you the connection string to copy and paste to deploy a new Anywhere environment.
Deletion steps involve the ACM and the server hosting your cluster. If necessary, first Reset Anywhere.
From the Altinity Cloud Manager:
example-cluster) and select OK.To list the ClickHouse namespaces, delete your Kubernetes managed environments from your server and run the following commands:
(NOTE: Make sure you have run the minikube start command first. )
# List the namespaces
kubectl get ns
# Delete the following in this order
kubectl -n altinity-cloud-managed-clickhouse delete chi --all
kubectl delete ns altinity-cloud-managed-clickhouse
kubectl delete ns altinity-cloud-system
Deleting a pod may be necessary if it is not starting up.
Problem
One of the pods won’t start.
(Example: see line 3 edge-proxy-66d44f7465-lxjjn)
┌──────────────── Pods(altinity-cloud-system)[8] ──────────────────────────┐
│ NAME↑ PF READY RESTARTS STATUS │
1 │ cloud-connect-d6ff8499f-bkc5k ● 1/1 3 Running │
2 │ crtd-665fd5cb85-wqkkk ● 1/1 3 Running │
3 │ edge-proxy-66d44f7465-lxjjn ● 1/2 7 CrashLoopBackOff │
4 │ grafana-5b466574d-4scjc ● 1/1 1 Running │
5 │ kube-state-metrics-58d86c747c-7hj79 ● 1/1 6 Running │
6 │ node-exporter-762b5 ● 1/1 3 Running │
7 │ prometheus-0 ● 1/1 3 Running │
8 │ statuscheck-f7c9b4d98-2jlt6 ● 1/1 3 Running │
└──────────────────────────────────────────────────────────────────────────┘
Terminal listing 1 - The pod in Line 3 edge-proxy-66d44f7465-lxjjn won’t start.
Solution
Delete the pod using the kubectl delete pod command and it will regenerate.
(Example: see line 3 edge-proxy-66d44f7465-lxjjn)
kubectl -n altinity-cloud-system delete pod edge-proxy-66d44f7465-lxjjn
To stop the Minikube service, run the following command:
minikube stop
✋ Stopping node "minikube" ...
🛑 1 node stopped.
This page shows how the Altinity Cloud Manager with an Altinity.Anywhere installation to remotely rescale a customer’s on-prem cluster.
The Ubuntu host the Kubernetes installation is installed on shows the various commmands use to verify the changes made from the ACM.
Select a cluster, then use the Actions > Rescale menu to bring up the Rescale Cluster window, then in the Desired Cluster Size, change the Number of Shards from 1 to 2 then press OK, then CONFIRM.
The nodes online pill box will show grey, 2/4 nodes online, then after several minutes, turn green showing 4/4 nodes online. If you do not see the grey 2/4 nodes online, and the nodes online is green and shows 2/2 nodes online, try the rescale operation again.
Ubuntu command kubectl -n altinity-cloud-managed-clickhouse... showing the Altinity clusters before the rescale operation.
kubectl -n <Altinity cluster name> running on-prem, that is managed from also by the ACM.
Ubuntu command kubectl get nodes before the rescale operation.
kubectl get nodes shows all the nodes on the Altinity ClickHouse cluster.
The newly spun up shard in cluster-x now reads 4/4 nodes online.
20 March 2023 · Read time 1 min
The following are instructions that can be used to install some of the prerequisites.
The following instructions are based on Install and Set Up kubectl on Linux
Download the kubectl binary:
curl -LO 'https://dl.k8s.io/release/v1.22.0/bin/linux/amd64/kubectl'
Verify the SHA-256 hash:
curl -LO "https://dl.k8s.io/v1.22.0/bin/linux/amd64/kubectl.sha256"
echo "$(<kubectl.sha256) kubectl" | sha256sum --check
Install kubectl into the /usr/local/bin directory (this assumes that your PATH includes use/local/bin):
sudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl
Verify the installation and the version:
kubectl version
Altinity.Cloud Anywhere Administraiton
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:
Kubernetes permissions:
See the steps in the Quickstart Connect to Altinity.Cloud procedure.
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 -
Locate your environment in the Environment tab in your Altinity.Cloud account.
Select ACTIONS->Delete.
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.
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
20 March 2023 · Read time 2 min
In order for Altinity.Cloud Anywhere to gather/store/query logs, you need to configure access to S3 or GCS bucket. Cloud-specific instructions provided below.
The recommended way is to use IRSA.
apiVersion: v1
kind: ServiceAccount
metadata:
name: log-storage
namespace: altinity-cloud-system
annotations:
eks.amazonaws.com/role-arn: "arn:aws:iam::<aws_account_id>:role/<role_arn>"
Alternatively, you can use custom Instance Profile or explicit credentials (shown below).
# create bucket
aws s3api create-bucket --bucket REPLACE_WITH_BUCKET_NAME --region REPLACE_WITH_AWS_REGION
# create user with access to the bucket
aws iam create-user --user-name REPLACE_WITH_USER_NAME
aws iam put-user-policy \
--user-name REPLACE_WITH_USER_NAME \
--policy-name REPLACE_WITH_POLICY_NAME \
--policy-document \
'{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"s3:ListBucket",
"s3:PutObject",
"s3:GetObject",
"s3:DeleteObject"
],
"Resource": [
"arn:aws:s3:::REPLACE_WITH_BUCKET_NAME",
"arn:aws:s3:::REPLACE_WITH_BUCKET_NAME/*"
],
"Effect": "Allow"
}
]
}'
# generate access key
aws iam create-access-key --user-name REPLACE_WITH_USER_NAME |
jq -r '"AWS_ACCESS_KEY_ID="+(.AccessKey.AccessKeyId)+"\nAWS_SECRET_ACCESS_KEY="+(.AccessKey.SecretAccessKey)+"\n"' > credentials.env
# create altinity-cloud-system/log-storage-aws secret containing AWS_ACCESS_KEY_ID & AWS_SECRET_ACCESS_KEY
kubectl create secret -n altinity-cloud-system generic log-storage-aws \
--from-env-file=credentials.env
rm -i credentials.env
Please send bucket name back to Altinity in order to finish configuration.
The recommended way is to use Workload Identity.
apiVersion: v1
kind: ServiceAccount
metadata:
name: log-storage
namespace: altinity-cloud-system
annotations:
iam.gke.io/gcp-service-account: "<gcp_sa_name>@<project_id>.iam.gserviceaccount.com"
Alternatively, you can use GCP service account for instance or explicit credentials (shown below).
# create bucket
gsutil mb gs://REPLACE_WITH_BUCKET_NAME
# create GCP SA with access to the bucket
gcloud iam service-accounts create REPLACE_WITH_GCP_SA_NAME \
--project=REPLACE_WITH_PROJECT_ID \
--display-name "REPLACE_WITH_DISPLAY_NAME"
gsutil iam ch \
serviceAccount:REPLACE_WITH_GCP_SA_NAME@REPLACE_WITH_PROJECT_ID.iam.gserviceaccount.com:roles/storage.admin \
gs://REPLACE_WITH_BUCKET_NAME
# generate GCP SA key
gcloud iam service-accounts keys create credentials.json \
--iam-account=REPLACE_WITH_GCP_SA_NAME@REPLACE_WITH_PROJECT_ID.iam.gserviceaccount.com \
--project=REPLACE_WITH_PROJECT_ID
# create altinity-cloud-system/log-storage-gcp secret containing credentials.json
kubectl create secret -n altinity-cloud-system generic log-storage-gcp \
--from-file=credentials.json
rm -i credentials.json
Please send bucket name back to Altinity in order to finish configuration.