Configure the cluster and vSphere credentials¶
Change the directory to the
kaas-bootstrapfolder created by the
Prepare deployment templates:
Contact your vSphere administrator to provide you with the values for the below parameters.
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.
vSphere cluster network parameters
Modify the following required network parameters:
IP address from the provided vSphere network for Kubernetes API load balancer (Keepalived VIP).
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.
To obtain the
LB_HOSTparameter for the selected vSphere network, contact your vSphere administrator who provides you with the IP ranges dedicated to your environment.
Modify other parameters if required. For example, add the corresponding values for
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
To obtain IPAM parameters for the selected vSphere network, contact your vSphere administrator who provides you with IP ranges dedicated to your environment only.
Enables IPAM. Recommended value is
truefor either DHCP or non-DHCP networks.
CIDR of the provided vSphere network. For example,
Gateway of the provided vSphere network.
IP range for the cluster machines. Specify the range of the provided CIDR. For example,
10.20.0.100-10.20.0.200. If the DHCP network is used, this range must not intersect with the DHCP range of the network.
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.
Configure MetalLB parameters:
Open the required configuration file for editing:
templates/vsphere/metallbconfig.yaml.template. For a detailed
MetalLBConfigobject description, see API Reference: MetalLBConfig resource.
SET_VSPHERE_METALLB_RANGEthat is the MetalLB range of IP addresses to assign to load balancers for Kubernetes Services.
To obtain the
VSPHERE_METALLB_RANGEparameter for the selected vSphere network, contact your vSphere administrator who provides you with the IP ranges dedicated to your environment.
For RHEL deployments, fill out
RHEL license configuration
Use 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 subscription 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 the 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>
For RHEL 8.7 TechPreview, verify mirrors configuration for your activation key. For more details, see RHEL 8 mirrors configuration.
Provide only one set of parameters. Mixing the 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.