Configure the cluster and vSphere credentials¶
Change the directory to the
kaas-bootstrapfolder created by the
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. 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.
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>
For RHEL 8.4 TechPreview, verify mirrors configuration for your activation key. For more details, see RHEL 8 mirrors configuration.
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.