1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00

Merge pull request #58235 from snarayan-redhat/OSDOCS-5525_RN

OSDOCS#5525: Release notes for remote workers support in vSphere
This commit is contained in:
Shubha Narayanan
2023-04-13 19:35:05 +05:30
committed by GitHub

View File

@@ -146,6 +146,11 @@ For more information, see xref:../updating/updating-cluster-prepare.adoc#updatin
==== Minimum required permissions for Microsoft Azure to install and delete an {product-title} cluster
In {product-title} {product-version}, instead of using the built-in roles, you can now define your custom roles to include the minimum required permissions for Microsoft Azure to install and delete an {product-title} cluster. These permissions are available for installer-provisioned infrastructure and user-provisioned infrastructure.
[id="ocp-4-13-install-configure-vips-to-run-on-control-plane"]
==== Configuring network components to run on the control plane in vSphere
If you need the virtual IP (VIP) addresses to run on the control plane nodes in a vSphere installation, you must configure the `ingressVIP` addresses to run exclusively on the control plane nodes. By default, {product-title} allows any node in the worker machine configuration pool to host the `ingressVIP` addresses. Because vSphere environments deploy worker nodes in separate subnets from the control plane nodes, configuring the `ingressVIP` addresses to run exclusively on the control plane nodes prevents issues from arising due to deploying worker nodes in separate subnets. For additional details, see xref:../installing/installing_vsphere/installing-vsphere-installer-provisioned-network-customizations.adoc#configure-network-components-to-run-on-the-control-plane_installing-vsphere-installer-provisioned-network-customizations[Configuring network components to run on the control plane in vSphere].
[id="ocp-4-13-post-installation"]
=== Post-installation configuration