This commit backports IFNAME key support from v1.1.1 of the
k8s containernetworking-plugins:
c16cff9805
IFNAME key support allows one to use the keyword
'IFNAME' in a network attachment definition using the
tuning plugin. Without this, the actual interface name
(whether specified in the pod spec, or the default 'net<X>')
must be specified.
Example:
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
name: hd0
spec:
config: '{
"cniVersion": "0.3.1",
"plugins": [
{
"name": "hd0",
"type": "host-device",
"device": "eth1000"
},
{
"type": "tuning",
"sysctl": {
"net.ipv6.conf.IFNAME.accept_ra": "0"
}
}
]
}'
The above example would disable the processing of
IPv6 router advertisements on the interface associated
with the network attachment definition, regardless of
what the interface has been named in the container.
Note: Currently, StarlingX supports v1.0.1 of the
containernetworking-plugins. Once the plugins have been
up-revved to v1.1.1, this patch can be removed.
Testing:
- Ensure patch is applied and build successful
on CentOS and Debian
- Perform a functional test of the tuning plugin using
the IFNAME key on CentOS and Debian
Story: 2010114
Task: 45693
Signed-off-by: Steven Webster <steven.webster@windriver.com>
Change-Id: I4fc617390b25bcf74a2a319fcb4409a0633c4a31
The spec file used here was from the Centos 7 src rpm for
containernetworking-plugins. The orig file is included to help show
modifications made to that spec file, to help understand which changes
were needed and to assist with future upversioning.
82b19f0a3c