TELCODOCS-328 - Adding new VIP install params for IPv4 and IPv6 #51135

rohennes · 2022-10-03T14:19:10Z

TELCODOCS-328: Ingress VIP and API VIP currently support IPv4 address only. With this update, IPv6 addresses are also supported.

Version(s):
4.12+

Issue:
https://issues.redhat.com/browse/TELCODOCS-328

Link to docs preview:
IPI updates

Updated install config code and added note:
http://file.emea.redhat.com/rohennes/TELCODOCS-328-dual-vips/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html#configuring-the-install-config-file_ipi-install-installation-workflow
Updated apiVIPs/IngressVIPs parameter definition and added a note in each definition:
http://file.emea.redhat.com/rohennes/TELCODOCS-328-dual-vips/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html#additional-install-config-parameters_ipi-install-installation-workflow
Updated dual-stack networking section:
http://file.emea.redhat.com/rohennes/TELCODOCS-328-dual-vips/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html#modifying-install-config-for-dual-stack-network_ipi-install-installation-workflow
Updated yaml code to match new params in this section:
http://file.emea.redhat.com/rohennes/TELCODOCS-328-dual-vips/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html#modifying-install-config-for-no-provisioning-network_ipi-install-installation-workflow

OpenStack updates

Updated note to change apiVIP to apiVIPs
http://file.emea.redhat.com/rohennes/TELCODOCS-328-dual-vips/installing/installing_openstack/installing-openstack-installer-custom.html#installation-osp-custom-subnet_installing-openstack-installer-custom
Update code snippet and added note about deprecation
http://file.emea.redhat.com/rohennes/TELCODOCS-328-dual-vips/installing/installing_openstack/installing-openstack-installer-custom.html#installation-osp-custom-subnet_installing-openstack-installer-custom

vSphere updates

RHV updates:

QE review:

QE has approved this change.

ocpdocs-previewbot · 2022-10-03T14:32:29Z

🤖 Updated build preview is available at:
https://51135--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/4140

cybertron

Mostly looks good. A few comments on the wording of the IP version requirements so we aren't implying anything that isn't supported.

cybertron · 2022-10-14T16:19:50Z

modules/ipi-install-additional-install-config-parameters.adoc

+
+[NOTE]
+====
+Before {product-title} 4.12, the cluster installation program accepted only an IPv4 address for the `apiVIP` configuration setting. From {product-title} 4.12 or later, the `apiVIP` configuration setting is deprecated. Instead, use a list format for the `apiVIPs` configuration setting to specify an IPv4 addresses, an IPv6 addresses or both IP address formats.


apiVIP accepted both ipv4 and ipv6 addresses. ipv6 was only for single-stack ipv6 deployments though.

cybertron · 2022-10-14T16:22:58Z

modules/ipi-install-additional-install-config-parameters.adoc

-| `apiVIP` | | (Optional) The virtual IP address for Kubernetes API communication.
+| `apiVIPs` | a| (Optional) The virtual IP address for Kubernetes API communication.
+
+This setting must either be provided in the `install-config.yaml` file as a reserved IP from the MachineNetwork or pre-configured in the DNS so that the default name resolves correctly. Use the virtual IP address and not the FQDN when adding a value to the `apiVIPs` configuration setting in the `install-config.yaml` file. The IP address must be from the primary IPv4 or IPv6 network when using dual-stack networking. If not set, the installation program uses `api.<cluster_name>.<base_domain>` to derive the IP address from the DNS.


"The IP address must be from the primary IPv4 or IPv6 network when using dual-stack networking."

In dual stack, the primary network must be ipv4. The requirements for ip version in the new config are:

ipv4 single stack: one ipv4 address
ipv6 single stack: one ipv6 address
dual stack: one ipv4 and optionally one ipv6 address, in that order

cybertron · 2022-10-14T16:28:46Z

modules/ipi-install-additional-install-config-parameters.adoc


-This setting must either be provided in the `install-config.yaml` file as a reserved IP from the MachineNetwork or pre-configured in the DNS so that the default name resolves correctly. Use the virtual IP address and not the FQDN when adding a value to the `ingressVIP` configuration setting in the `install-config.yaml` file. The IP address must be from the primary IPv4 network when using dual stack networking. If not set, the installer uses `test.apps.<cluster_name>.<base_domain>` to derive the IP address from the DNS.
+This setting must either be provided in the `install-config.yaml` file as a reserved IP from the MachineNetwork or pre-configured in the DNS so that the default name resolves correctly. Use the virtual IP address and not the FQDN when adding a value to the `ingressVIP` configuration setting in the `install-config.yaml` file. The IP address must be from the primary IPv4 or IPv6 network when using dual-stack networking. If not set, the installation program uses `test.apps.<cluster_name>.<base_domain>` to derive the IP address from the DNS.


The same IP requirements apply here too.

cybertron · 2022-10-14T16:29:16Z

modules/ipi-install-additional-install-config-parameters.adoc


+[NOTE]
+====
+Before {product-title} 4.12, the cluster installation program accepted only an IPv4 address for the `ingressVIP` configuration setting. From {product-title} 4.12 or later, the `ingressVIP` configuration setting is deprecated. Instead, use a list format for the `ingressVIPs` configuration setting to specify an IPv4 addresses, an IPv6 addresses or both IP address formats.


Likewise here.

cybertron · 2022-10-14T16:30:52Z

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


+You can also configure IPv4 or IPv6 virtual IP (VIP) address endpoints for the Ingress VIP and API VIP. This provides an interface to the cluster for applications that use IPv4 or IPv6 addresses.   


This should probably be "IPv4 and IPv6". In dual stack you can't have just an IPv6 VIP.

cybertron · 2022-10-14T16:31:56Z

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

+
+.Procedure
+
+. Edit the `machineNetwork`, `clusterNetwork`, and `serviceNetwork` configuration settings in the `install-config.yaml` file to configure IPv4 or IPv6 address endpoints for nodes in the cluster. Each setting must have two CIDR entries each. Ensure the first CIDR entry is the IPv4 setting and the second CIDR entry is the IPv6 setting.


This should also be an "and".

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

+    ingressVIPs:
+      - <wildcard_ipv4>
+      - <wildcard_ipv6>
+----


cybertron · 2022-10-20T20:13:30Z

/lgtm

All of the ip version requirements look good now, thanks!

openshift-ci · 2022-10-21T12:13:55Z

New changes are detected. LGTM label has been removed.

creydr · 2022-11-02T07:08:28Z

modules/installation-configuration-parameters.adoc

@@ -1233,12 +1233,24 @@ Additional {rh-virtualization} configuration parameters are described in the fol
 |Required. The vNIC profile ID of the VM network interfaces. This can be inferred if the cluster network has a single profile.
 |String. For example: `3fa86930-0be5-4052-b667-b79f0a729692`

-|`platform.ovirt.api_vip`
+|`platform.ovirt.api_vips`
 |Required. An IP address on the machine network that will be assigned to the API virtual IP (VIP). You can access the OpenShift API at this endpoint.


Actually it is possible to specify up to two IP addresses (in dual-stack case). Same applies for the other apiVips and ingressVips fields.

Thanks @creydr - I have implemented your feedback. Please let me know if this is accurate or if any other issues. Thanks!

creydr · 2022-11-02T07:18:08Z

modules/installing-rhv-example-install-config-yaml.adoc

+    api_vips: 
+      - 10.46.8.230
+    ingress_vips: 
+      - 192.168.1.5


IIRC the ovirt people wanted to check their config first and remove the validation, if the validation is wrong: https://coreos.slack.com/archives/C68TNFWA2/p1663242301646269?thread_ts=1662377646.622669&cid=C68TNFWA2 - anyhow I haven't seen an exception for ovirt in the installer for the validation.
@mburman5 how did you proceed on the IP expected to be in one of the machine networks issue on ovirt?

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

eldar101 · 2022-11-02T12:35:36Z

Other than a small comment above,
/lgtm.

rohennes · 2022-11-09T10:43:46Z

/label telco
/label peer-review-needed

abhatt-rh · 2022-11-09T15:59:59Z

/label peer-review-in-progress

abhatt-rh

Hi @rohennes,
Nice work!
I added a few comments for your consideration.

/remove-label peer-review-in-progress
/remove-label peer-review-needed
/label peer-review-done

abhatt-rh · 2022-11-11T11:43:46Z

modules/installation-configuration-parameters.adoc

+
+[NOTE]
+====
+From {product-title} 4.12 or later, the `api_vip` configuration setting is deprecated. Instead, use a list format to enter a value in the `api_vips` configuration setting. The order of the list indicates the primary and secondary VIP address for each service.


Global comment based on the general usage across OpenShift docs:

Suggested change

From {product-title} 4.12 or later, the `api_vip` configuration setting is deprecated. Instead, use a list format to enter a value in the `api_vips` configuration setting. The order of the list indicates the primary and secondary VIP address for each service.

In {product-title} 4.12 and later, the `api_vip` configuration setting is deprecated. Instead, use a list format to enter a value in the `api_vips` configuration setting. The order of the list indicates the primary and secondary VIP address for each service.

abhatt-rh · 2022-11-11T11:47:59Z

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

@@ -148,6 +150,11 @@ specify the base64-encoded user name and password for your mirror registry.
 <12> Provide the `imageContentSources` section from the output of the command to mirror the repository.
 endif::restricted[]

+[NOTE]
+====
+From {product-title} 4.12 or later, the `apiVIP` and `IngressVIP` configuration settings are deprecated. Instead, use a list format to enter values in the `apiVIPs` and `IngressVIPs` configuration settings.


Suggested change

From {product-title} 4.12 or later, the `apiVIP` and `IngressVIP` configuration settings are deprecated. Instead, use a list format to enter values in the `apiVIPs` and `IngressVIPs` configuration settings.

From {product-title} 4.12 or later, the `apiVIP` and `ingressVIP` configuration settings are deprecated. Instead, use a list format to enter values in the `apiVIPs` and `ingressVIPs` configuration settings.

abhatt-rh · 2022-11-11T11:52:46Z

modules/installing-rhv-example-install-config-yaml.adoc

+
+[NOTE]
+====
+From {product-title} 4.12 or later, the `apiVIP` and `IngressVIP` configuration settings are deprecated. Instead, use a list format to enter values in the `apiVIPs` and `IngressVIPs` configuration settings.


For RHV, should these be as suggested?

Suggested change

From {product-title} 4.12 or later, the `apiVIP` and `IngressVIP` configuration settings are deprecated. Instead, use a list format to enter values in the `apiVIPs` and `IngressVIPs` configuration settings.

From {product-title} 4.12 or later, the `api_vip` and `ingress_vip` configuration settings are deprecated. Instead, use a list format to enter values in the `api_vips` and `ingress_vips` configuration settings.

abhatt-rh · 2022-11-11T11:53:53Z

modules/installing-rhv-example-install-config-yaml.adoc

@@ -111,6 +120,10 @@ pullSecret: '{"auths": ...}'
 sshKey: ssh-ed12345 AAAA...
 ----

+[NOTE]
+====
+From {product-title} 4.12 or later, the `apiVIP` and `IngressVIP` configuration settings are deprecated. Instead, use a list format to enter values in the `apiVIPs` and `IngressVIPs` configuration settings.


For RHV, should these be as suggested?

Suggested change

From {product-title} 4.12 or later, the `apiVIP` and `IngressVIP` configuration settings are deprecated. Instead, use a list format to enter values in the `apiVIPs` and `IngressVIPs` configuration settings.

From {product-title} 4.12 or later, the `api_vip` and `ingress_vip` configuration settings are deprecated. Instead, use a list format to enter values in the `api_vips` and `ingress_vips` configuration settings.

Yes, good catch.

abhatt-rh · 2022-11-11T14:47:48Z

modules/ipi-install-additional-install-config-parameters.adoc


-This setting must either be provided in the `install-config.yaml` file as a reserved IP from the MachineNetwork or pre-configured in the DNS so that the default name resolves correctly. Use the virtual IP address and not the FQDN when adding a value to the `ingressVIP` configuration setting in the `install-config.yaml` file. The IP address must be from the primary IPv4 network when using dual stack networking. If not set, the installer uses `test.apps.<cluster_name>.<base_domain>` to derive the IP address from the DNS.
+This setting must either be provided in the `install-config.yaml` file as a reserved IP from the MachineNetwork or pre-configured in the DNS so that the default name resolves correctly. Use the virtual IP address and not the FQDN when adding a value to the `ingressVIP` configuration setting in the `install-config.yaml` file. The primary IP address must be from the IPv4 network when using dual stack networking. If not set, the installation program uses `test.apps.<cluster_name>.<base_domain>` to derive the IP address from the DNS.


Suggested change

This setting must either be provided in the `install-config.yaml` file as a reserved IP from the MachineNetwork or pre-configured in the DNS so that the default name resolves correctly. Use the virtual IP address and not the FQDN when adding a value to the `ingressVIP` configuration setting in the `install-config.yaml` file. The primary IP address must be from the IPv4 network when using dual stack networking. If not set, the installation program uses `test.apps.<cluster_name>.<base_domain>` to derive the IP address from the DNS.

This setting must either be provided in the `install-config.yaml` file as a reserved IP from the MachineNetwork or pre-configured in the DNS so that the default name resolves correctly. Use the virtual IP address and not the FQDN when adding a value to the `ingressVIPs` configuration setting in the `install-config.yaml` file. The primary IP address must be from the IPv4 network when using dual stack networking. If not set, the installation program uses `test.apps.<cluster_name>.<base_domain>` to derive the IP address from the DNS.

abhatt-rh · 2022-11-11T15:00:08Z

modules/installing-rhv-example-install-config-yaml.adoc

@@ -157,6 +172,11 @@ pullSecret: '{"auths": ...}'
 sshKey: ssh-ed25519 AAAA...
 ----

+[NOTE]
+====
+From {product-title} 4.12 or later, the `apiVIP` and `IngressVIP` configuration settings are deprecated. Instead, use a list format to enter values in the `apiVIPs` and `IngressVIPs` configuration settings.


Same as above

Suggested change

From {product-title} 4.12 or later, the `apiVIP` and `IngressVIP` configuration settings are deprecated. Instead, use a list format to enter values in the `apiVIPs` and `IngressVIPs` configuration settings.

From {product-title} 4.12 or later, the `api_vip` and `ingress_vip` configuration settings are deprecated. Instead, use a list format to enter values in the `api_vips` and `ingress_vips` configuration settings.

abhatt-rh · 2022-11-11T15:04:23Z

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

@@ -6,7 +6,7 @@
 [id='modifying-install-config-for-dual-stack-network_{context}']
 = Optional: Deploying with dual-stack networking

-To deploy an {product-title} cluster with dual-stack networking, edit the `machineNetwork`, `clusterNetwork`, and `serviceNetwork` configuration settings in the `install-config.yaml` file. Each setting must have two CIDR entries each. Ensure the first CIDR entry is the IPv4 setting and the second CIDR entry is the IPv6 setting.
+For dual-stack networking in {product-title} clusters, you can configure IPv4 and IPv6 address endpoints for nodes in the cluster. Edit the `machineNetwork`, `clusterNetwork`, and `serviceNetwork` configuration settings in the `install-config.yaml` file to configure IPv4 and IPv6 address endpoints for nodes in the cluster. Each setting must have two CIDR entries each. Ensure the first CIDR entry is the IPv4 setting and the second CIDR entry is the IPv6 setting.


It’s usually best to put the action first. Consider the suggested change:

Suggested change

For dual-stack networking in {product-title} clusters, you can configure IPv4 and IPv6 address endpoints for nodes in the cluster. Edit the `machineNetwork`, `clusterNetwork`, and `serviceNetwork` configuration settings in the `install-config.yaml` file to configure IPv4 and IPv6 address endpoints for nodes in the cluster. Each setting must have two CIDR entries each. Ensure the first CIDR entry is the IPv4 setting and the second CIDR entry is the IPv6 setting.

For dual-stack networking in {product-title} clusters, you can configure IPv4 and IPv6 address endpoints for nodes in the cluster. To configure IPv4 and IPv6 address endpoints for nodes in the cluster, edit the `machineNetwork`, `clusterNetwork`, and `serviceNetwork` configuration settings in the `install-config.yaml` file. Each setting must have two CIDR entries each. Ensure the first CIDR entry is the IPv4 setting and the second CIDR entry is the IPv6 setting.

cybertron

LGTM modulo the comments from @abhatt-rh

cybertron · 2022-11-11T16:02:56Z

modules/installing-rhv-example-install-config-yaml.adoc

@@ -111,6 +120,10 @@ pullSecret: '{"auths": ...}'
 sshKey: ssh-ed12345 AAAA...
 ----

+[NOTE]
+====
+From {product-title} 4.12 or later, the `apiVIP` and `IngressVIP` configuration settings are deprecated. Instead, use a list format to enter values in the `apiVIPs` and `IngressVIPs` configuration settings.


Yes, good catch.

rohennes · 2022-11-28T13:21:44Z

/label merge-review-needed

EricPonvelle · 2022-11-28T15:43:12Z

/cherrypick enterprise-4.12

openshift-cherrypick-robot · 2022-11-28T15:43:58Z

@EricPonvelle: new pull request created: #53215

In response to this:

/cherrypick enterprise-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

openshift-ci bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Oct 3, 2022

rohennes force-pushed the TELCODOCS-328-dual-vips branch 3 times, most recently from 11456c1 to 1a4e04a Compare October 4, 2022 13:27

openshift-ci bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Oct 4, 2022

rohennes force-pushed the TELCODOCS-328-dual-vips branch 5 times, most recently from 7a62177 to 9dd093d Compare October 4, 2022 14:15

cybertron reviewed Oct 14, 2022

View reviewed changes

rohennes force-pushed the TELCODOCS-328-dual-vips branch 2 times, most recently from 25fbba2 to f3d3af4 Compare October 17, 2022 11:31

rohennes commented Oct 17, 2022

View reviewed changes

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

ingressVIPs:

- <wildcard_ipv4>

- <wildcard_ipv6>

----

This comment was marked as resolved.

Sign in to view

rohennes mentioned this pull request Oct 17, 2022

TELCODOCS-328 - RN for IPv6 support for VIPs #51737

Merged

1 task

openshift-ci bot assigned cybertron Oct 20, 2022

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 20, 2022

rohennes force-pushed the TELCODOCS-328-dual-vips branch from f3d3af4 to ef607ed Compare October 21, 2022 12:13

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 21, 2022

rohennes force-pushed the TELCODOCS-328-dual-vips branch 5 times, most recently from 54d0ba6 to ef018a9 Compare October 28, 2022 15:19

openshift-ci bot removed the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Oct 28, 2022

creydr reviewed Nov 2, 2022

View reviewed changes

rohennes force-pushed the TELCODOCS-328-dual-vips branch 2 times, most recently from afc1c72 to 5815095 Compare November 2, 2022 12:15

eldar101 reviewed Nov 2, 2022

View reviewed changes

modules/installation-installer-provisioned-vsphere-config-yaml.adoc Show resolved Hide resolved

rohennes force-pushed the TELCODOCS-328-dual-vips branch from 5815095 to 58b85c9 Compare November 4, 2022 16:57

openshift-ci bot added telco Label for all Telco PRs peer-review-needed Signifies that the peer review team needs to review this PR labels Nov 9, 2022

openshift-ci bot added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Nov 9, 2022

abhatt-rh reviewed Nov 11, 2022

View reviewed changes

openshift-ci bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR peer-review-needed Signifies that the peer review team needs to review this PR labels Nov 11, 2022

cybertron reviewed Nov 11, 2022

View reviewed changes

Adding new VIP install configs for IPv4 and IPv6

e5e73fc

rohennes force-pushed the TELCODOCS-328-dual-vips branch from 58b85c9 to e5e73fc Compare November 28, 2022 11:34

openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Nov 28, 2022

EricPonvelle added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Nov 28, 2022

EricPonvelle merged commit 9a89e6b into openshift:main Nov 28, 2022

openshift-cherrypick-robot mentioned this pull request Nov 28, 2022

[enterprise-4.12] TELCODOCS-328 - Adding new VIP install params for IPv4 and IPv6 #53215

Merged

EricPonvelle removed the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Nov 28, 2022

rohennes mentioned this pull request Dec 15, 2022

TELCODOCS-874: New feature release notes for Metal platform for 4.12 #53814

Closed

1 task

bergerhoffer added the branch/enterprise-4.12 label Jan 10, 2023

bergerhoffer added this to the Planned for 4.12 GA milestone Jan 10, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

TELCODOCS-328 - Adding new VIP install params for IPv4 and IPv6 #51135

TELCODOCS-328 - Adding new VIP install params for IPv4 and IPv6 #51135

rohennes commented Oct 3, 2022 •

edited

ocpdocs-previewbot commented Oct 3, 2022 •

edited

cybertron left a comment

cybertron Oct 14, 2022

cybertron Oct 14, 2022

cybertron Oct 14, 2022

cybertron Oct 14, 2022

cybertron Oct 14, 2022

cybertron Oct 14, 2022

This comment was marked as resolved.

cybertron commented Oct 20, 2022

openshift-ci bot commented Oct 21, 2022

creydr Nov 2, 2022

rohennes Nov 2, 2022

creydr Nov 2, 2022

eldar101 commented Nov 2, 2022

rohennes commented Nov 9, 2022

abhatt-rh commented Nov 9, 2022

abhatt-rh left a comment

abhatt-rh Nov 11, 2022

abhatt-rh Nov 11, 2022

abhatt-rh Nov 11, 2022

abhatt-rh Nov 11, 2022

cybertron Nov 11, 2022

abhatt-rh Nov 11, 2022

abhatt-rh Nov 11, 2022

abhatt-rh Nov 11, 2022

cybertron left a comment

cybertron Nov 11, 2022

rohennes commented Nov 28, 2022

EricPonvelle commented Nov 28, 2022

openshift-cherrypick-robot commented Nov 28, 2022


		This setting must either be provided in the `install-config.yaml` file as a reserved IP from the MachineNetwork or pre-configured in the DNS so that the default name resolves correctly. Use the virtual IP address and not the FQDN when adding a value to the `ingressVIP` configuration setting in the `install-config.yaml` file. The IP address must be from the primary IPv4 network when using dual stack networking. If not set, the installer uses `test.apps.<cluster_name>.<base_domain>` to derive the IP address from the DNS.
		This setting must either be provided in the `install-config.yaml` file as a reserved IP from the MachineNetwork or pre-configured in the DNS so that the default name resolves correctly. Use the virtual IP address and not the FQDN when adding a value to the `ingressVIP` configuration setting in the `install-config.yaml` file. The IP address must be from the primary IPv4 or IPv6 network when using dual-stack networking. If not set, the installation program uses `test.apps.<cluster_name>.<base_domain>` to derive the IP address from the DNS.


		You can also configure IPv4 or IPv6 virtual IP (VIP) address endpoints for the Ingress VIP and API VIP. This provides an interface to the cluster for applications that use IPv4 or IPv6 addresses.


		.Procedure

		. Edit the `machineNetwork`, `clusterNetwork`, and `serviceNetwork` configuration settings in the `install-config.yaml` file to configure IPv4 or IPv6 address endpoints for nodes in the cluster. Each setting must have two CIDR entries each. Ensure the first CIDR entry is the IPv4 setting and the second CIDR entry is the IPv6 setting.

	From {product-title} 4.12 or later, the `api_vip` configuration setting is deprecated. Instead, use a list format to enter a value in the `api_vips` configuration setting. The order of the list indicates the primary and secondary VIP address for each service.
	In {product-title} 4.12 and later, the `api_vip` configuration setting is deprecated. Instead, use a list format to enter a value in the `api_vips` configuration setting. The order of the list indicates the primary and secondary VIP address for each service.

TELCODOCS-328 - Adding new VIP install params for IPv4 and IPv6 #51135

TELCODOCS-328 - Adding new VIP install params for IPv4 and IPv6 #51135

Conversation

rohennes commented Oct 3, 2022 • edited

ocpdocs-previewbot commented Oct 3, 2022 • edited

cybertron left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

This comment was marked as resolved.

cybertron commented Oct 20, 2022

openshift-ci bot commented Oct 21, 2022

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

eldar101 commented Nov 2, 2022

rohennes commented Nov 9, 2022

abhatt-rh commented Nov 9, 2022

abhatt-rh left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

cybertron left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rohennes commented Nov 28, 2022

EricPonvelle commented Nov 28, 2022

openshift-cherrypick-robot commented Nov 28, 2022

rohennes commented Oct 3, 2022 •

edited

ocpdocs-previewbot commented Oct 3, 2022 •

edited