openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

CNV-62830: Updated note about IPv6 single-stack support

Browse Source
This commit is contained in:
Shikha Jhala
2025-06-02 09:35:17 -04:00
committed by openshift-cherrypick-robot
parent 56845ede86
commit e47b23d59b
2 changed files with 11 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
virt/install/preparing-cluster-for-virt.adoc
View File

@@ -20,8 +20,13 @@ You can use any installation method, including user-provisioned, installer-provi
If you deploy {VirtProductName} with {rh-storage-first}, you must create a dedicated storage class for Windows virtual machine disks. See link:https://access.redhat.com/articles/6978371[Optimizing ODF PersistentVolumes for Windows VMs] for details.
IPv6::
You cannot run {VirtProductName} on a single-stack IPv6 cluster.
{VirtProductName} support for single-stack IPv6 clusters is limited to the OVN-Kubernetes localnet and Linux bridge Container Network Interface (CNI) plugins.
====
:FeatureName: Deploying {VirtProductName} on a single-stack IPv6 cluster
include::snippets/technology-preview.adoc[]
:!FeatureName:
endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
// Hiding in ROSA/OSD as FIPS not supported

9
virt/vm_networking/virt-networking-overview.adoc
View File

@@ -8,10 +8,11 @@ toc::[]
{VirtProductName} provides advanced networking functionality by using custom resources and plugins. Virtual machines (VMs) are integrated with {product-title} networking and its ecosystem.
[NOTE]
====
You cannot run {VirtProductName} on a single-stack IPv6 cluster.
====
{VirtProductName} support for single-stack IPv6 clusters is limited to the OVN-Kubernetes localnet and Linux bridge Container Network Interface (CNI) plugins.
:FeatureName: Deploying {VirtProductName} on a single-stack IPv6 cluster
include::snippets/technology-preview.adoc[]
The following figure illustrates the typical network setup of {VirtProductName}. Other configurations are also possible.