You can deploy an additional regional VMWare vSphere-based cluster on top of the AWS or vSphere management cluster to create managed clusters with different configurations if required.
To deploy a vSphere-based regional cluster:
Log in to the node where you bootstrapped a management cluster.
Verify access to the target vSphere cluster from Docker. For example:
docker run --rm alpine sh -c "apk add --no-cache curl; \
curl https://vsphere.server.com"
The system output must contain no error records. In case of issues, follow the steps provided in Troubleshooting.
Prepare your RHEL license and deployment templates:
Fill out templates/vsphere/rhellicenses.yaml.template
using one of the following set of parameters for RHEL machines subscription:
The user name and password of your RedHat Customer Portal account associated with your RHEL license for Virtual Datacenters.
Optionally, provide the subscription allocation pools to use for the RHEL
subscriptions activation. If not needed, remove the poolIDs field
for subscription-manager to automatically select the licenses for
machines.
For example:
spec:
username: <username>
password:
value: <password>
poolIDs:
- <pool1>
- <pool2>
Available since 2.6.0 The activation key and organization ID associated with your RedHat account with RHEL license for Virtual Datacenters. The activation key can be created by the organization administrator on RedHat Customer Portal.
If you use the RedHat Satellite server for management of your RHEL infrastructure, you can provide a pre-generated activation key from that server. In this case, also provide the URL to the RedHat Satellite RPM for installation of the CA certificate that belongs to that server.
For example:
spec:
activationKey:
value: <activation key>
orgID: "<organization ID>"
rpmUrl: <rpm url>
Caution
Provide only one set of parameters. Mixing of parameters from different activation methods will cause deployment failure.
Modify templates/vsphere/vsphere-config.yaml.template:
Parameter |
Description |
|---|---|
|
IP address or FQDN of the vCenter Server. |
|
Port of the vCenter Server. For example, |
|
vSphere data center name. |
|
Flag that controls validation of the vSphere Server certificate.
Must be |
|
vSphere Cluster API provider user name that you added when preparing the deployment user setup and permissions. |
|
vSphere Cluster API provider user password. |
|
vSphere Cloud Provider deployment user name that you added when preparing the deployment user setup and permissions. |
|
vSphere Cloud Provider deployment user password. |
Modify the templates/vsphere/cluster.yaml.template parameters
to fit your deployment. For example, add the corresponding values
for cidrBlocks in the spec::clusterNetwork::services section.
Parameter |
Description |
|---|---|
|
IP address from the provided vSphere network for load balancer (Keepalived). |
|
MetalLB range of IP addresses that can be assigned to load balancers for Kubernetes Services. |
|
Name of the vSphere datastore. You can use different datastores for vSphere Cluster API and vSphere Cloud Provider. |
|
Path to a folder where the cluster machines metadata will be stored. |
|
Path to a network for cluster machines. |
|
Path to a resource pool in which VMs will be created. |
Note
The passwordSalt and passwordHash values for the IAM
roles are automatically re-generated during the IAM
configuration.
Starting from Container Cloud 2.6.0, if a vSphere network has no DHCP
server, provide the following additional parameters for a proper
network setup on machines using embedded IP address management (IPAM)
in templates/vsphere/cluster.yaml.template:
Parameter |
Description |
|---|---|
|
Enables IPAM. Set to |
|
CIDR of the provided vSphere network. For example, |
|
Gateway of the provided vSphere network. |
|
Optional. IP range for the cluster machines. Specify the range of the provided CIDR.
For example, |
|
Optional. IP ranges to be excluded from being assigned to the cluster
machines. The MetalLB range and |
|
List of nameservers for the provided vSphere network. |
Optional. Configure the regional NTP server parameters to be applied to all machines of regional and managed clusters in the specified region.
In templates/vsphere/cluster.yaml.template, add the ntp:servers
section with the list of required servers names:
spec:
...
providerSpec:
value:
kaas:
...
regional:
- helmReleases:
- name: vsphere-provider
values:
config:
lcm:
...
ntp:
servers:
- 0.pool.ntp.org
...
provider: vsphere
...
Prepare the OVF template as described in Prepare the OVF template.
In templates/vsphere/machines.yaml.template:
Define SET_VSPHERE_TEMPLATE_PATH prepared in the previous step.
Modify other parameters as required.
spec:
providerSpec:
value:
apiVersion: vsphere.cluster.k8s.io/v1alpha1
kind: VsphereMachineProviderSpec
rhelLicense: kaas-mgmt-rhel-license
network:
devices:
- dhcp4: true
dhcp6: false
template: <SET_VSPHERE_TEMPLATE_PATH>
Note
The <rhel-license-name> value is the RHEL license name defined
in rhellicenses.yaml.tempalte, defaults to
kaas-mgmt-rhel-license.
Optional. 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:
HTTP_PROXY
HTTPS_PROXY
NO_PROXY
Example snippet:
export HTTP_PROXY=http://proxy.example.com:3128
export HTTPS_PROXY=http://user:pass@proxy.example.com:3128
export NO_PROXY=172.18.10.0,registry.internal.lan
The following variables formats are accepted:
Variable |
Format |
|---|---|
|
|
|
Comma-separated list of IP addresses or domain names |
For the list of Mirantis resources and IP addresses to be accessible from the Container Cloud clusters, see Reference Architecture: Hardware and system requirements.
Export the following parameters:
export KAAS_VSPHERE_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.
Run the regional cluster bootstrap script:
./bootstrap.sh deploy_regional
Note
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.
# |
Description |
|---|---|
1 |
Prepare the bootstrap cluster for the new regional cluster. |
2 |
Load the updated Container Cloud CRDs for |
3 |
Connect to each machine of the management cluster through SSH. |
4 |
Wait for the |
5 |
Load the following objects to the new regional cluster: |
6 |
Forward the bootstrap cluster endpoint to |
7 |
Wait for all CRDs to be available and verify the objects created using these CRDs. |
8 |
Pivot the cluster API stack to the regional cluster. |
9 |
Switch the LCM agent from the bootstrap cluster to the regional one. |
10 |
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 a managed cluster.