-
Notifications
You must be signed in to change notification settings - Fork 799
Add chaining tuning plugin #3587
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
base: master
Are you sure you want to change the base?
Conversation
|
|
||
| // Add IPv6 disable sysctls when DISABLE_POD_V6 is enabled | ||
| if disablePodV6 { | ||
| sysctls["net.ipv6.conf.all.disable_ipv6"] = "1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need to explicitly add these?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because VPC CNI currently use tuning CN plugin to disable ipv6. This is just keeping that feature
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i wonder if i need to move this lower and override any tuning configs
|
|
||
| Example: | ||
| ``` | ||
| TUNING_SYSCTLS='{"net.core.somaxconn":"1024","net.ipv4.tcp_max_syn_backlog":"2048"}' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TOL does user have to provide value through env var? what will be experience if we had config map?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This wasn't completely sure about. I was thinking env var however config map could work too however I didn't want to add a whole new config map just for this because it seems over kill
What type of PR is this?
feature
Which issue does this PR fix?:
#3586
What does this PR do / Why do we need it?:
Testing done on this change:
Will this PR introduce any new dependencies?:
Will this break upgrades or downgrades? Has updating a running cluster been tested?:
Does this change require updates to the CNI daemonset config files to work?:
Does this PR introduce any user-facing change?:
Yes.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.