remove kube_proxy_conntrack_max var (#7971)
This commit is contained in:
parent
1edb7d771f
commit
62ab477838
1 changed files with 0 additions and 4 deletions
|
@ -24,10 +24,6 @@ kube_proxy_client_qps: 5
|
||||||
kube_proxy_config_sync_period: 15m0s
|
kube_proxy_config_sync_period: 15m0s
|
||||||
|
|
||||||
### Conntrack
|
### Conntrack
|
||||||
# max is the maximum number of NAT connections to track (0 to
|
|
||||||
# leave as-is). This takes precedence over maxPerCore and min.
|
|
||||||
kube_proxy_conntrack_max: 'null'
|
|
||||||
|
|
||||||
# maxPerCore is the maximum number of NAT connections to track
|
# maxPerCore is the maximum number of NAT connections to track
|
||||||
# per CPU core (0 to leave the limit as-is and ignore min).
|
# per CPU core (0 to leave the limit as-is and ignore min).
|
||||||
kube_proxy_conntrack_max_per_core: 32768
|
kube_proxy_conntrack_max_per_core: 32768
|
||||||
|
|
Loading…
Reference in a new issue