-
Notifications
You must be signed in to change notification settings - Fork 790
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.
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
Allow setting sysctls on a particular interface #669
Conversation
Signed-off-by: Piotr Skamruk <[email protected]>
3384f6e
to
c16cff9
Compare
/lgtm |
@jellonek could you also update the documentation at https://github.com/containernetworking/cni.dev/blob/main/content/plugins/current/meta/tuning.md with this new behavior? |
An argument can be made that tuning plugin should have been interface specific from the beginning, that is, each e.g. |
@dcbw done: containernetworking/cni.dev#92 |
I'm wondering whether replacing |
@mccv1r0 imo we should move discussion about if we want or not limiting changing sysctls only to apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
name: enable-forwarding
spec:
config: '{
"cniVersion": "0.3.1",
"plugins": [
{
"type": "loopback"
},
{
"name": "enable-forwarding",
"type": "tuning",
"sysctl": {
"net.ipv4.conf.all.forwarding": "1",
"net.ipv6.conf.all.forwarding": "1",
"net.ipv6.conf.default.forwarding":"1",
"net.ipv6.conf.default.disable_ipv6":"0",
"net.ipv6.conf.all.disable_ipv6": "0",
"net.ipv4.conf.default.rp_filter": "2",
"net.ipv4.conf.all.rp_filter": "2"
}
}
]
}' |
/lgtm |
As in subject.