Configuring Network Access

Defining network connections for your environment

The CONFIGURE menu lets you define network connections for your cluster. Clicking the Network menu item takes you to the Environment Network Configuration dialog:

Here are the details of these fields:

Subnets CIDR

This is used in Bring Your Own Cloud (BYOC) environments. You define subnets in your cloud account, then reference them when you use the ACM to create a Kubernetes cluster in your cloud account. The subnets you provided when you defined the environment appear here.

Load Balancer Type

The default value (and likely the only value available) is Altinity Edge Ingress. If your cloud provider is AWS, AWS NLB may be an option as well. In some cases, you’ll see checkboxes that let you enable the load balancer for public and/or private traffic. If you need to use a different load balancer, contact Altinity support.

NOTE: If you choose a Private load balancer, changes to your ClickHouse configurations will not be automatically updated:

You’ll need to publish any changes manually. See the Publishing a Cluster's Configuration page for the details.

VPC Endpoints Account ID

This option is only available for environments that are running on AWS and have a private load balancer enabled.

LB Proxy Protocol

Enabling this item disables the MySQL protocol.

SNI Proxy

In an Altinity.Cloud Anywhere environment, the endpoints the ACM needs to access may not be publicly accessible. This field lets you define an SNI proxy to route requests from the ACM to the correct endpoint inside your Altinity.Cloud Anywhere environment. (Server Name Indication is an extension to TLS that allows multiple hostnames to be served over a single HTTP endpoint.)