TELCODOCS-2529: In IBI and IBU, IPv6/4 now both possible as primary address fam in dual-stack networking #101313

rohennes · 2025-10-29T15:33:01Z

TELCODOCS-2529: In IBI and IBU, IPv6/4 now both possible as primary address fam in dual-stack networking

Version(s):
4.20+

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

Link to docs preview:

QE review:

QE has approved this change.

openshift-ci-robot · 2025-10-29T15:33:05Z

@rohennes: This pull request references TELCODOCS-2529 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20" instead.

In response to this:

TELCODOCS-2529: In IBI and IBU, IPv6/4 now both possible as primary address fam in dual-stack networking

Version(s):
4.20+

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

Link to docs preview:

QE review:

QE has approved this change.

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 openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2025-10-29T15:33:14Z

@rohennes: This pull request references TELCODOCS-2529 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20" instead.

In response to this:

TELCODOCS-2529: In IBI and IBU, IPv6/4 now both possible as primary address fam in dual-stack networking

Version(s):
4.20+

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

Link to docs preview:

QE review:

QE has approved this change.

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 openshift-eng/jira-lifecycle-plugin repository.

ocpdocs-previewbot · 2025-10-29T15:47:48Z

🤖 Tue Nov 04 15:31:58 - Prow CI generated the docs preview:

https://101313--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/image_base_install/ibi_deploying_sno_clusters/ibi-edge-image-based-install.html
https://101313--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/image_base_install/ibi_deploying_sno_clusters/ibi-edge-image-based-install-standalone.html

danmanor · 2025-10-30T07:45:17Z

modules/ibi-create-config-iso.adoc

 <4> Specify the hostname for the cluster.
 <5> Specify the name of the `ClusterImageSet` resource you used to define the container release images to use for deployment.
-<6> Specify the public Classless Inter-Domain Routing (CIDR) of the external network. For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format. Regardless of the list order, the IPv4 family becomes the primary address family.
+<6> Specify the public Classless Inter-Domain Routing (CIDR) of the external network. For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format.


Maybe we should add that the first address is the primary and it must match the primary IP stack of the seed

danmanor · 2025-10-30T07:46:15Z

modules/ibi-create-standalone-config-iso.adoc

 sshKey: 'ssh-rsa <your_ssh_pub_key>'
 ----
-<1> For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format. You must specify the IPv4 family as the primary address family by defining the IPv4 address as the first item in the list.
+<1> For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format.


Sam comment as above

danmanor · 2025-10-30T07:46:48Z

modules/ibi-image-cluster-install-api-spec.adoc

 |`bareMetalHostRef`|`string`| Specify the `bareMetalHost` resource to use for the cluster deployment

-|`machineNetwork`|`string`| Specify the public Classless Inter-Domain Routing (CIDR) of the external network. For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format. Regardless of the list order, the IPv4 family becomes the primary address family.
+|`machineNetwork`|`string`| Specify the public Classless Inter-Domain Routing (CIDR) of the external network. For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format.


trewest · 2025-11-04T14:55:21Z

modules/ibi-image-cluster-install-api-spec.adoc

 |`bareMetalHostRef`|`string`| Specify the `bareMetalHost` resource to use for the cluster deployment

-|`machineNetwork`|`string`| Specify the public Classless Inter-Domain Routing (CIDR) of the external network. For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format. Regardless of the list order, the IPv4 family becomes the primary address family.
+|`machineNetwork`|`string`| Specify the public Classless Inter-Domain Routing (CIDR) of the external network. For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format. The first CIDR in the list is the primary address family and must match the primary address family of the seed cluster.


Suggested change

|`machineNetwork`|`string`| Specify the public Classless Inter-Domain Routing (CIDR) of the external network. For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format. The first CIDR in the list is the primary address family and must match the primary address family of the seed cluster.

|`machineNetworks`|`string`| Specify the public Classless Inter-Domain Routing (CIDR) of the external network. For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format. The first CIDR in the list is the primary address family and must match the primary address family of the seed cluster.

Nice spot!! Updated

…al-stack networking

openshift-ci · 2025-11-04T15:32:49Z

@rohennes: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

openshift-ci-robot · 2025-11-04T17:41:29Z

@rohennes: This pull request references TELCODOCS-2529 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20" instead.

In response to this:

TELCODOCS-2529: In IBI and IBU, IPv6/4 now both possible as primary address fam in dual-stack networking

Version(s):
4.20+

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

Link to docs preview:

QE review:

QE has approved this change.

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 openshift-eng/jira-lifecycle-plugin repository.

slovern · 2025-11-04T17:43:14Z

/cherrypick enterprise-4.21

slovern · 2025-11-04T17:43:21Z

/cherrypick enterprise-4.20

openshift-cherrypick-robot · 2025-11-04T17:44:06Z

@slovern: new pull request created: #101717

In response to this:

/cherrypick enterprise-4.21

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-sigs/prow repository.

openshift-cherrypick-robot · 2025-11-04T17:44:16Z

@slovern: new pull request created: #101719

In response to this:

/cherrypick enterprise-4.20

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-sigs/prow repository.

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 29, 2025

openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 29, 2025

danmanor reviewed Oct 30, 2025

View reviewed changes

rohennes force-pushed the TELCODOCS-2529 branch from 9f810db to 0c5c3a1 Compare October 30, 2025 10:27

danmanor approved these changes Oct 30, 2025

View reviewed changes

trewest reviewed Nov 4, 2025

View reviewed changes

In IBI and IBU, IPv6/4 now both possible as primary address fam in du…

a26b543

…al-stack networking

rohennes force-pushed the TELCODOCS-2529 branch from 0c5c3a1 to a26b543 Compare November 4, 2025 15:19

trewest approved these changes Nov 4, 2025

View reviewed changes

slovern added branch/enterprise-4.20 branch/enterprise-4.21 labels Nov 4, 2025

slovern merged commit 3778eb3 into openshift:main Nov 4, 2025
2 checks passed

openshift-cherrypick-robot mentioned this pull request Nov 4, 2025

[enterprise-4.21] TELCODOCS-2529: In IBI and IBU, IPv6/4 now both possible as primary address fam in dual-stack networking #101717

Merged

openshift-cherrypick-robot mentioned this pull request Nov 4, 2025

[enterprise-4.20] TELCODOCS-2529: In IBI and IBU, IPv6/4 now both possible as primary address fam in dual-stack networking #101719

Merged

slovern added this to the Continuous Release milestone Nov 4, 2025

	\|`machineNetwork`\|`string`\| Specify the public Classless Inter-Domain Routing (CIDR) of the external network. For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format. The first CIDR in the list is the primary address family and must match the primary address family of the seed cluster.
	\|`machineNetworks`\|`string`\| Specify the public Classless Inter-Domain Routing (CIDR) of the external network. For dual-stack networking, you can specify both IPv4 and IPv6 CIDRs using a list format. The first CIDR in the list is the primary address family and must match the primary address family of the seed cluster.

TELCODOCS-2529: In IBI and IBU, IPv6/4 now both possible as primary address fam in dual-stack networking #101313

TELCODOCS-2529: In IBI and IBU, IPv6/4 now both possible as primary address fam in dual-stack networking #101313

Uh oh!

Conversation

rohennes commented Oct 29, 2025 • edited by slovern Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Oct 29, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Oct 29, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ocpdocs-previewbot commented Oct 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

danmanor Oct 30, 2025

Choose a reason for hiding this comment

Uh oh!

danmanor Oct 30, 2025

Choose a reason for hiding this comment

Uh oh!

danmanor Oct 30, 2025

Choose a reason for hiding this comment

Uh oh!

trewest Nov 4, 2025

Choose a reason for hiding this comment

Uh oh!

rohennes Nov 4, 2025

Choose a reason for hiding this comment

Uh oh!

openshift-ci bot commented Nov 4, 2025

Uh oh!

openshift-ci-robot commented Nov 4, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

slovern commented Nov 4, 2025

Uh oh!

slovern commented Nov 4, 2025

Uh oh!

openshift-cherrypick-robot commented Nov 4, 2025

Uh oh!

openshift-cherrypick-robot commented Nov 4, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

rohennes commented Oct 29, 2025 •

edited by slovern

Loading

openshift-ci-robot commented Oct 29, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Oct 29, 2025 •

edited by openshift-ci bot

Loading

ocpdocs-previewbot commented Oct 29, 2025 •

edited

Loading

openshift-ci-robot commented Nov 4, 2025 •

edited by openshift-ci bot

Loading