Skip to content

Commit 7ff945c

Browse files
authored
Merge pull request #49647 from dougbtv/interface-sysctls
Tuning CNI IFNAME clarification (omits using eth0)
2 parents 370bd9e + 94d19d6 commit 7ff945c

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

modules/nodes-safe-sysctls-list.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,5 +111,5 @@ a| Define behavior for gratuitous ARP frames with an IPv6 address that is not al
111111

112112
[NOTE]
113113
====
114-
The interface name is represented by the `IFNAME` token, and is replaced with the actual name of the interface at runtime.
114+
When setting these values using the `tuning` CNI plugin, use the value `IFNAME` literally. The interface name is represented by the `IFNAME` token, and is replaced with the actual name of the interface at runtime.
115115
====

nodes/containers/nodes-containers-sysctls.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Sysctl settings are exposed through Kubernetes, allowing users to modify certain
1111
Network sysctls are a special category of sysctl. Network sysctls include:
1212

1313
* System-wide sysctls, for example `net.ipv4.ip_local_port_range`, that are valid for all networking. You can set these independently for each pod on a node.
14-
* Interface-specific sysctls, for example `net.ipv4.conf.eth0.accept_local`, that only apply to a specific interface. You cannot set these independently for each pod on a node. You set these by using a configuration in the `tuning-cni` after the network interfaces are created.
14+
* Interface-specific sysctls, for example `net.ipv4.conf.IFNAME.accept_local`, that only apply to a specific additional network interface for a given pod. You can set these independently for each additional network configuration. You set these by using a configuration in the `tuning-cni` after the network interfaces are created.
1515
1616
Moreover, only those sysctls considered _safe_ are whitelisted by default; you
1717
can manually enable other _unsafe_ sysctls on the node to be available to the
@@ -51,4 +51,4 @@ include::modules/nodes-containers-sysctls-unsafe.adoc[leveloffset=+1]
5151
[id="additional-resources_nodes-containers-sysctls"]
5252
== Additional resources
5353

54-
* xref:../../networking/setting-interface-level-network-sysctls.adoc#nodes-setting-interface-level-network-sysctls[Setting interface-level network sysctls]
54+
* xref:../../networking/setting-interface-level-network-sysctls.adoc#nodes-setting-interface-level-network-sysctls[Setting interface-level network sysctls]

0 commit comments

Comments
 (0)