Bootstrap a management cluster¶
After you complete the prerequisite steps described in Prerequisites, proceed with bootstrapping your VMware vSphere-based Mirantis Container Cloud management cluster.
To bootstrap a vSphere-based management cluster:
Log in to the bootstrap node running Ubuntu 18.04 that is configured as described in Prerequisites.
Prepare the bootstrap script:
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
Change the directory to the
kaas-bootstrapfolder created by the script.
Obtain your license file that will be required during the bootstrap:
Create a user account at www.mirantis.com.
Log in to your account and download the
Save the license file as
kaas-bootstrapdirectory on the bootstrap node.
Prepare deployment templates:
IP address or FQDN of the vCenter Server.
Port of the vCenter Server. For example,
port: "8443". Leave empty to use
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.
templates/vsphere/cluster.yaml.templateparameters to fit your deployment. For example, add the corresponding values for
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.
For either DHCP or non-DHCP vSphere network:
Determine the vSphere network parameters as described in VMware vSphere network objects and IPAM recommendations.
Provide the following additional parameters for a proper network setup on machines using embedded IP address management (IPAM) in
Enables IPAM. Set to
truefor networks without DHCP.
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
SET_LB_HOSTshould not intersect with the addresses for IPAM. For example,
List of nameservers for the provided vSphere network.
For RHEL deployments, fill out
templates/vsphere/rhellicenses.yaml.templateusing 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
subscription-managerto automatically select the licenses for machines.
spec: username: <username> password: value: <password> poolIDs: - <pool1> - <pool2>
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:
Provide the URL to the RedHat Satellite RPM for installation of the CA certificate that belongs to that server.
squid-proxyon the management or regional cluster to allow access to your Satellite server. For details, see Configure squid-proxy.
spec: activationKey: value: <activation key> orgID: "<organization ID>" rpmUrl: <rpm url>
Provide only one set of parameters. Mixing of parameters from different activation methods will cause deployment failure.
For CentOS deployments, in
templates/vsphere/rhellicenses.yaml.template, remove all lines under
bootstrap.env, add the
KAAS_VSPHERE_ENABLED=trueenvironment variable that enables the vSphere provider deployment in Container Cloud.
Configure the regional NTP server parameters to be applied to all machines of regional and managed clusters in the specified region.
templates/vsphere/cluster.yaml.template, add the
ntp:serverssection 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.
SET_VSPHERE_TEMPLATE_PATHprepared in the previous step
Modify other parameters as required
spec: providerSpec: value: apiVersion: vsphere.cluster.k8s.io/v1alpha1 kind: VsphereMachineProviderSpec rhelLicense: <rhel-license-name> network: devices: - dhcp4: true dhcp6: false template: <SET_VSPHERE_TEMPLATE_PATH>
<rhel-license-name>value is the RHEL license name defined in
rhellicenses.yaml.tempalte, defaults to
kaas-mgmt-rhel-license. Remove or comment out this parameter for CentOS deployments.
If you require all Internet access to go through a proxy server, in
bootstrap.env, add the following environment variables to bootstrap the management and regional cluster using proxy:
export HTTP_PROXY=http://proxy.example.com:3128 export HTTPS_PROXY=http://user:firstname.lastname@example.org:3128 export NO_PROXY=172.18.10.0,registry.internal.lan
The following variables formats are accepted:
http://proxy.example.com:port- for anonymous access
http://user:email@example.com:port- for restricted access
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 Requirements for a VMware vSphere-based cluster.
Optional. Configure external identity provider for IAM.
Optional. If you are going to use your own TLS certificates for Keycloak, set
Run the bootstrap script:
In case of deployment issues, refer to Troubleshooting. If the script fails for an unknown reason:
Run the cleanup script:
Rerun the bootstrap script.
If the bootstrap fails on the Connecting to bootstrap cluster step with the unable to initialize Tiller in bootstrap cluster: failed to establish connection with tiller error, refer to the known issue 16873 to identify possible root cause of the issue and apply the workaround, if applicable.
When the bootstrap is complete, collect and save the following management cluster details in a secure location:
kubeconfigfile located in the same directory as the bootstrap script. This file contains the admin credentials for the management cluster.
ssh_keyfor access to the management cluster nodes that is located in the same directory as the bootstrap script.
If the initial version of your Container Cloud management cluster was earlier than 2.6.0,
openstack_tmpand is located at
The URL for the Container Cloud web UI. Before the first login, create users with required permissions as described in Create initial users after a management cluster bootstrap.
The StackLight endpoints. For details, see Access StackLight web UIs.
The Keycloak URL that the system outputs when the bootstrap completes. The admin password for Keycloak is located in
kaas-bootstrap/passwords.ymlalong with other IAM passwords.
The Container Cloud web UI communicates with Keycloak to authenticate users. Keycloak is exposed using HTTPS and self-signed TLS certificates that are not trusted by web browsers.
To use your own TLS certificates for Keycloak, refer to Configure TLS certificates for management cluster applications.
When the bootstrap is complete, the bootstrap cluster resources are freed up.
Now, you can proceed with operating your management cluster using the Container Cloud web UI and deploying managed clusters as described in Create and operate a VMware vSphere-based managed cluster.