Deploy an Equinix Metal based regional cluster with public networking¶
Since Container Cloud 2.18.0, the public networking mode for the Equinix Metal based clusters is deprecated for the sake of the private networking mode. Deployments with public networks will become unsupported in one of the following Container Cloud releases.
You can deploy an additional regional Equinix Metal based cluster with public networking to create managed clusters of several provider types or with different configurations.
To deploy an Equinix Metal based regional cluster:
Configure BGP for your Equinix Metal project as described in Equinix Metal project setup.
Log in to the node where you bootstrapped the Container Cloud management cluster.
Verify that the bootstrap directory is updated.
Select from the following options:
For clusters deployed using Container Cloud 2.11.0 or later:
./container-cloud bootstrap download --management-kubeconfig <pathToMgmtKubeconfig> \ --target-dir <pathToBootstrapDirectory>
For clusters deployed using the Container Cloud release earlier than 2.11.0 or if you deleted the
kaas-bootstrapfolder, download and run the Container Cloud bootstrap script:
wget https://binary.mirantis.com/releases/get_container_cloud.sh chmod 0755 get_container_cloud.sh ./get_container_cloud.sh
Prepare the Equinix Metal configuration for the new regional cluster:
Change the directory to
spec:apiToken:valueusing the values obtained in the previous steps. For example:
spec: projectID: g98sd6f8-dc7s-8273-v8s7-d9v7395nd91 apiToken: value: Bi3m9c7qjYBD3UgsnSCSsqs2bYkbK
templates/equinix/cluster.yaml.template, modify the default configuration of the Equinix Metal
facilitydepending on the previously prepared capacity settings:
providerSpec: value: ... facility: am6
Also, modify other parameters as required.
templates/equinix/machines.yaml.template, modify the default configuration of the Equinix Metal machine type. The minimal required type is
providerSpec: value: ... machineType: c3.small.x86
Also, modify other parameters as required.
If you require all Internet access to go through a proxy server, in
bootstrap.env, add the following environment variables to bootstrap the regional cluster using proxy:
export HTTP_PROXY=http://proxy.example.com:3128 export HTTPS_PROXY=http://user:email@example.com:3128 export NO_PROXY=172.18.10.0,registry.internal.lan export PROXY_CA_CERTIFICATE_PATH="/home/ubuntu/.mitmproxy/mitmproxy-ca-cert.cer"
The following variables formats are accepted:
http://proxy.example.com:port- for anonymous access
http://user:firstname.lastname@example.org:port- for restricted access
Comma-separated list of IP addresses or domain names
PROXY_CA_CERTIFICATE_PATHAvailable since 2.18.0 as TechPreview
Optional. Path to the proxy CA certificate for man-in-the-middle (MITM) proxies. Must be placed on the bootstrap node to be trusted. For details, see Install a CA certificate for a MITM proxy on a bootstrap node.
If you require Internet access to go through a MITM proxy, ensure that the proxy has streaming enabled as described in Enable streaming for MITM.
For the list of Mirantis resources and IP addresses to be accessible from the Container Cloud clusters, see Requirements for an Equinix Metal based cluster.
Optional if servers from the Ubuntu NTP pool (
*.ubuntu.pool.ntp.org) are accessible from the node where the regional cluster is being provisioned. Otherwise, this step is mandatory.
Configure the regional NTP server parameters to be applied to all machines of regional and managed clusters in the specified region.
templates/equinix/cluster.yaml.template, add the
ntp:serverssection with the list of required servers names:
spec: ... providerSpec: value: kaas: ... regional: - helmReleases: - name: equinix-provider values: config: lcm: ... ntp: servers: - 0.pool.ntp.org ... provider: equinixmetal ...
Optional. Technology Preview. As of Container Cloud 2.18.0, enable Kubernetes network encryption by adding the following field to the
spec: providerSpec: value: secureOverlay: true
For more details, see MKE documentation: Kubernetes network encryption.
Export the following parameters:
export KAAS_EQUINIX_ENABLED=true export KUBECONFIG=<pathToMgmtClusterKubeconfig> export REGIONAL_CLUSTER_NAME=<newRegionalClusterName> export REGION=<NewRegionName>
Substitute the parameters enclosed in angle brackets with the corresponding values of your cluster.
REGIONAL_CLUSTER_NAMEparameters values must contain only lowercase alphanumeric characters, hyphens, or periods.
If the bootstrap node for the regional cluster deployment is not the same where you bootstrapped the management cluster, also export
SSH_KEY_NAME. It is required for the management cluster to create a
publicKeyKubernetes CRD with the public part of your newly generated
ssh_keyfor the regional cluster.
Run the regional cluster bootstrap script:
When the bootstrap is complete, obtain and save in a secure location the
kubeconfig-<regionalClusterName>file located in the same directory as the bootstrap script. This file contains the admin credentials for the regional cluster.
If the bootstrap node for the regional cluster deployment is not the same where you bootstrapped the management cluster, a new regional
ssh_keywill be generated. Make sure to save this key in a secure location as well.
Prepare the bootstrap cluster for the new regional cluster.
Load the updated Container Cloud CRDs for
Machineswith information about the new regional cluster to the management cluster.
Connect to each machine of the management cluster through SSH.
Wait for the
Clusterobjects of the new regional cluster to be ready on the management cluster.
Load the following objects to the new regional cluster:
Secretwith the management cluster
ClusterRolefor the Container Cloud provider.
Forward the bootstrap cluster endpoint to
Wait for all CRDs to be available and verify the objects created using these CRDs.
Pivot the cluster API stack to the regional cluster.
Switch the LCM Agent from the bootstrap cluster to the regional one.
Wait for the Container Cloud components to start on the regional cluster.
Now, you can proceed with deploying the managed clusters of supported provider types as described in Create and operate managed clusters.