installing-vsphere-installer-provisioned-network-customizations.adoc

Installing a cluster on vSphere with network customizations

In {product-title} version {product-version}, you can install a cluster on your VMware vSphere instance by using installer-provisioned infrastructure with customized network configuration options. By customizing your network configuration, your cluster can coexist with existing IP address allocations in your environment and integrate with existing MTU and VXLAN configurations. To customize the installation, you modify parameters in the install-config.yaml file before you install the cluster.

You must set most of the network configuration parameters during installation, and you can modify only kubeProxy configuration parameters in a running cluster.

Prerequisites

• You have completed the tasks in Preparing to install a cluster using installer-provisioned infrastructure.

• You reviewed your VMware platform licenses. Red Hat does not place any restrictions on your VMware licenses, but some VMware infrastructure components require licensing.

• You reviewed details about the {product-title} installation and update processes.

• You read the documentation on selecting a cluster installation method and preparing it for users.

• You provisioned persistent storage for your cluster. To deploy a private image registry, your storage must provide ReadWriteMany access modes.

• The {product-title} installer requires access to port 443 on the vCenter and ESXi hosts. You verified that port 443 is accessible.

• If you use a firewall, confirm with the administrator that port 443 is accessible. Control plane nodes must be able to reach vCenter and ESXi hosts on port 443 for the installation to succeed.

• If you use a firewall, you configured it to allow the sites that your cluster requires access to.

  Note	Be sure to also review this site list if you are configuring a proxy.

modules/cluster-entitlements.adoc

modules/installation-vsphere-regions-zones.adoc

Additional resources

• Additional VMware vSphere configuration parameters

• Deprecated VMware vSphere configuration parameters

• vSphere automatic migration

• VMware vSphere CSI Driver Operator

modules/installation-initializing.adoc

Additional resources

• Installation configuration parameters

modules/installation-installer-provisioned-vsphere-config-yaml.adoc

modules/installation-configure-proxy.adoc

modules/ipi-install-modifying-install-config-for-dual-stack-network.adoc

modules/configuring-vsphere-regions-zones.adoc

modules/installation-vsphere-multiple-nics.adoc

Additional resources

• Network configuration parameters

modules/nw-network-config.adoc

modules/nw-modifying-operator-install-config.adoc

modules/nw-operator-vsphere-multiple-subnets.adoc

Additional resources

• Cluster Network Operator configuration

• .spec.platformSpec.vsphere.nodeNetworking

modules/nw-operator-cr.adoc

modules/nw-osp-services-external-load-balancer.adoc

modules/nw-osp-configuring-external-load-balancer.adoc

modules/installation-launching-installer.adoc

modules/cli-logging-in-kubeadmin.adoc

Creating registry storage

After you install the cluster, you must create storage for the registry Operator.

modules/registry-removed.adoc

modules/installation-registry-storage-config.adoc

modules/registry-configuring-storage-vsphere.adoc

modules/installation-registry-storage-block-recreate-rollout.adoc

For instructions about configuring registry storage so that it references the correct PVC, see Configuring the registry for vSphere.

modules/cluster-telemetry.adoc

Additional resources

• See About remote health monitoring for more information about the Telemetry service

modules/ipi-install-configure-network-components-to-run-on-the-control-plane.adoc

Next steps

• Customize your cluster.

• If necessary, you can opt out of remote health reporting.

• Set up your registry and configure registry storage.

• Optional: View the events from the vSphere Problem Detector Operator to determine if the cluster has permission or storage configuration issues.