You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/installation-network-user-infra.adoc
+9Lines changed: 9 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -87,6 +87,15 @@ endif::ibm-z[]
87
87
ifndef::ibm-z[]
88
88
During the initial boot, the machines require an IP address configuration that is set either through a DHCP server or statically by providing the required boot options. After a network connection is established, the machines download their Ignition config files from an HTTP or HTTPS server. The Ignition config files are then used to set the exact state of each machine. The Machine Config Operator completes more changes to the machines, such as the application of new certificates or keys, after installation.
89
89
90
+
Use a DHCP server for the long-term management of the machines for your cluster. Ensure that the DHCP server is configured to provide persistent IP addresses, DNS server information, and hostnames to the cluster machines. As a cluster administrator, ensure that you reserve the following IP addresses components that interact with the DHCP server:
91
+
92
+
* Two unique virtual IP (VIP) addresses. One VIP address for the API endpoint and one VIP address for the wildcard ingress endpoint.
93
+
* One IP address for the provisioner node.
94
+
* An IP address for each control plane node.
95
+
* An IP address for each compute node.
96
+
97
+
If you have multiple network interfaces that interact with a bonded interface, reserve the same IP addresses for these multiple network interfaces so to ensure better load balancing, fault tolerance, and bandwidth capabilites for your cluster network infrastructure.
98
+
90
99
[NOTE]
91
100
====
92
101
* It is recommended to use a DHCP server for long-term management of the cluster machines. Ensure that the DHCP server is configured to provide persistent IP addresses, DNS server information, and hostnames to the cluster machines.
Copy file name to clipboardExpand all lines: modules/installation-user-infra-machines-static-network.adoc
+8-23Lines changed: 8 additions & 23 deletions
Original file line number
Diff line number
Diff line change
@@ -287,9 +287,14 @@ ifndef::ibm-z[]
287
287
[discrete]
288
288
=== Bonding multiple SR-IOV network interfaces to a dual port NIC interface
289
289
290
-
Optional: You can bond multiple SR-IOV network interfaces to a dual port NIC interface by using the `bond=` option.
290
+
As an optional configuration, you can bond multiple SR-IOV network interfaces to a dual port NIC interface by using the `bond=` option. To apply this configuration to your cluster, complete the procedure steps for each node that runs on your cluster.
291
291
292
-
On each node, you must perform the following tasks:
292
+
[IMPORTANT]
293
+
====
294
+
If your network configuration includes an Open vSwitch (OVS) interface and you enabled `active-backup` bond mode, you must specify a Media Access Control (MAC) address failover. This configuration prevents node communication issues with the bonded interfaces, such as `eno1f0` and `eno2f0`.
295
+
====
296
+
297
+
.Procedure
293
298
294
299
ifndef::installing-ibm-power[]
295
300
. Create the SR-IOV virtual functions (VFs) following the guidance in link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_virtualization/managing-virtual-devices_configuring-and-managing-virtualization#managing-sr-iov-devices_managing-virtual-devices[Managing SR-IOV devices]. Follow the procedure in the "Attaching SR-IOV networking devices to virtual machines" section.
@@ -314,6 +319,7 @@ The following examples illustrate the syntax you must use:
314
319
----
315
320
bond=bond0:eno1f0,eno2f0:mode=active-backup
316
321
ip=bond0:dhcp
322
+
fail_over_mac=1
317
323
----
318
324
319
325
** To configure the bonded interface to use a static IP address, enter the specific IP address you want and related information. For example:
@@ -393,12 +399,6 @@ a|Override the Ignition platform ID for the installed system.
393
399
a|`--console <spec>`
394
400
a|Set the kernel and bootloader console for the installed system. For more information about the format of `<spec>`, see the link:https://www.kernel.org/doc/html/latest/admin-guide/serial-console.html[Linux kernel serial console] documentation.
395
401
396
-
a|`--append-karg <arg>...`
397
-
a|Append a default kernel argument to the installed system.
398
-
399
-
a|`--delete-karg <arg>...`
400
-
a|Delete a default kernel argument from the installed system.
401
-
402
402
a|`-n`, `--copy-network`
403
403
a|Copy the network configuration from the install environment.
404
404
@@ -464,12 +464,6 @@ a|Specify the kernel and bootloader console for the destination system.
464
464
a|`--dest-device <path>`
465
465
a|Install and overwrite the specified destination device.
466
466
467
-
a|`--dest-karg-append <arg>`
468
-
a|Add a kernel argument to each boot of the destination system.
469
-
470
-
a|`--dest-karg-delete <arg>`
471
-
a|Delete a kernel argument from each boot of the destination system.
472
-
473
467
a|`--network-keyfile <path>`
474
468
a|Configure networking by using the specified NetworkManager keyfile for live and destination systems.
475
469
@@ -488,15 +482,6 @@ a|Apply the specified installer configuration file.
488
482
a|`--live-ignition <path>`
489
483
a|Merge the specified Ignition config file into a new configuration fragment for the live environment.
490
484
491
-
a|`--live-karg-append <arg>`
492
-
a|Add a kernel argument to each boot of the live environment.
493
-
494
-
a|`--live-karg-delete <arg>`
495
-
a|Delete a kernel argument from each boot of the live environment.
496
-
497
-
a|`--live-karg-replace <k=o=n>`
498
-
a|Replace a kernel argument in each boot of the live environment, in the form `key=old=new`.
Copy file name to clipboardExpand all lines: modules/nw-understanding-networking-service-to-pod.adoc
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Key concepts of service-to-pod communication include:
28
28
29
29
Services use selectors to identify the pods that should receive the traffic. The selectors match labels on the pods to determine which pods are part of the service. Example: A service with the selector `app: myapp` will route traffic to all pods with the label `app: myapp`.
30
30
31
-
Endpoints are dynamically updated to reflect the current IP addresses of the pods that match the service selector. {product-name} maintains these endpoints and ensures that the service routes traffic to the correct pods.
31
+
Endpoints are dynamically updated to reflect the current IP addresses of the pods that match the service selector. {product-title} maintains these endpoints and ensures that the service routes traffic to the correct pods.
32
32
33
33
The communication flow refers to the sequence of steps and interactions that occur when a service in Kubernetes routes traffic to the appropriate pods. The typical communication flow for service-to-pod communication is as follows:
0 commit comments