Skip to content

OCPBUGS-57620: Added warning to Configuring host network interfaces a… #94995

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-57620: Added warning to Configuring host network interfaces a… #94995

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
9 changes: 7 additions & 2 deletions ...nstall-configuring-host-network-interfaces-in-the-install-config.yaml-file.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,11 @@ Before installation, you can set the `networkConfig` configuration setting in th

The most common use case for this functionality is to specify a static IP address on the bare-metal network, but you can also configure other networks such as a storage network. This functionality supports other NMState features such as VLAN, VXLAN, bridges, bonds, routes, MTU, and DNS resolver settings.

[WARNING]
====
When specifying DNS resolver settings in the `networkConfig` configuration, do not set the `rotate` option. The `rotate` setting causes `api-int.<cluster_name>.<base_domain>` DNS lookup failures because Multus pods get stuck in the `ContainerCreating` state and the Multus container network interface (CNI) fails.
====

.Prerequisites

* Configure a `PTR` DNS record with a valid hostname for each node with a static IP address.
Expand All @@ -28,7 +33,7 @@ If you use a provisioning network, configure it by using the `dnsmasq` tool in I
====
Errors in the YAML syntax might result in a failure to apply the network configuration. Additionally, maintaining the validated YAML syntax is useful when applying changes by using Kubernetes NMState after deployment or when expanding the cluster.
====

+
.. Create an NMState YAML file:
+
[source,yaml]
Expand All @@ -54,7 +59,7 @@ routes:
----
+
<1> Replace `<nic1_name>`, `<ip_address>`, `<dns_ip_address>`, `<next_hop_ip_address>` and `<next_hop_nic1_name>` with appropriate values.

+
.. Test the configuration file by running the following command:
+
[source,terminal]
Expand Down