Skip to content

OCPBUGS#38977: Added a limitation for disabling IPv6 OVNK #96014

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

OCPBUGS#38977: Added a limitation for disabling IPv6 OVNK #96014

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions modules/nw-ovn-kuberentes-limitations.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@

The OVN-Kubernetes network plugin has the following limitations:

* If you set `ipv6.disable=1` for the `kernelArgument` parameter in the `MachineConfig` custom resource (CR) for your cluster, OVN-Kubernetes pods enter a `CrashLoopBackOff` state. Additionally, updating your cluster to a later version of {product-title} fails because the Network Operator is stuck on a `Degraded` state. Red{nbsp}Hat does not support disabling IPv6 adddresses for your cluster so do not set `ipv6.disable=1` for the `kernelArgument` parameter.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a suggestion.
I feel there's some scope to simplify this sentence where we don't have to mention about ipv6.disable twice. Since we are calling it out as a limitation, we can avoid being prescriptive about the not setting the parameter.

Suggested change
* If you set `ipv6.disable=1` for the `kernelArgument` parameter in the `MachineConfig` custom resource (CR) for your cluster, OVN-Kubernetes pods enter a `CrashLoopBackOff` state. Additionally, updating your cluster to a later version of {product-title} fails because the Network Operator is stuck on a `Degraded` state. Red{nbsp}Hat does not support disabling IPv6 adddresses for your cluster so do not set `ipv6.disable=1` for the `kernelArgument` parameter.
* If you set `ipv6.disable` to `1` for the `kernelArgument` parameter in the `MachineConfig` custom resource (CR) for your cluster, OVN-Kubernetes pods enter a `CrashLoopBackOff` state. Additionally, updating your cluster to a later version of {product-title} fails because the Network Operator is stuck on a `Degraded` state. Red{nbsp}Hat does not support disabling IPv6 adddresses for your cluster so do not set `ipv6.disable=1` for the `kernelArgument` parameter.


// The foll limitation is also recorded in the installation section.
ifndef::microshift[]
* For clusters configured for dual-stack networking, both IPv4 and IPv6 traffic must use the same network interface as the default gateway.
Expand Down