Configuring Kubernetes
The Kubernetes tab, as you would expect, lets you configure Kubernetes settings:
Figure 1 - The Kubernetes tab
Here are the details of these fields:
Master API URL
Under normal circumstances this value should not be changed. It can be useful in a Bring Your Own Kubernetes environment when defining connections between the ACM and Kubernetes. Contact Altinity support for help setting this up.
Auth Options - TLS Handshake + Token
This authentication scheme is the most common:
Figure 2 - Using the TLS Handshake and Token authentication scheme
The Client Key and Client Cert are defined for you. Under normal circumstances, you won’t need to change these values at all.
Auth Options - No Auth (Proxy)
This approach is used for development purposes only. It should never be used in production.
Figure 3 - Using the No Auth authentication scheme
Auth Options - Access Token
This is a legacy technique that is no longer used. It will be removed in a future version of the ACM.
Figure 4 - Using the Access Token authentication scheme
Namespace
The namespace used for the ClickHouse clusters deployed by Altinity. The default value is altinity-cloud-managed-clickhouse
. Once the ClickHouse cluster is created, the namespace cannot be changed.
Manage Namespace
If this switch is turned on, namespaces will be managed by the ACM.
Certificate ARN
The ARN (Amazon Resource Name) for the certificate used by this environment. This is managed for you in Altinity.Cloud environments, and is typically not needed in an Altinity.Cloud Anywhere environment.
Node Scope Label
Defines a label that will be added to nodes created by the ACM. This is useful for Kubernetes clusters that have user-created nodes. With a node scope label, the ACM will only deploy pods to nodes with that label.
Node Zone Key
Defines a zone key for this environment. For example, specifying us-east-1c
generates the label topology.kubernetes.io/zone: "us-east-1c"
. See the Kubernetes documentation for more information.
K8S Dashboard URL
You have the option of installing a Kubernetes monitoring tool inside the Kubernetes cluster that hosts your ClickHouse clusters. If you do, enter the URL of the monitoring tool here. Most customers use tools that run outside the Kubernetes cluster (k9s, for example), so this option is rarely used.
Server Startup Time
Depending on the number of tables and the amount of data in your ClickHouse cluster, it may take longer than normal to start. That means it’s possible that the Kubernetes cluster hosting your ClickHouse cluster will delete and restart the pods needed to run ClickHouse before ClickHouse can start. For that reason, you can define a startup time, which is the number of seconds the Kubernetes cluster should wait for your ClickHouse cluster to start.
Use Operator Managed PVs
If selected, the persistent volumes used by your ClickHouse clusters will be managed by the Altinity Kubernetes Operator. This is the default; only legacy Altinity.Cloud environments should disable this option.