Skip to content
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

Configurable IPVS timeouts #6395

Closed
fulii opened this issue Jul 14, 2020 · 0 comments · Fixed by #6396
Closed

Configurable IPVS timeouts #6395

fulii opened this issue Jul 14, 2020 · 0 comments · Fixed by #6396
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@fulii
Copy link
Contributor

fulii commented Jul 14, 2020

What would you like to be added:

  • I'd like the option to configure IPVS timeouts in the role/kubernetes/master/templates/kubeadm-config.v1beta2.yaml.j2 file.
  • With changing the template for kubeproxy.config.k8s.io/v1alpha1/KubeProxyConfiguration manifest.

Current:

ipvs:
  excludeCIDRs: {{ kube_proxy_exclude_cidrs }}
  minSyncPeriod: {{ kube_proxy_min_sync_period }}
  scheduler: {{ kube_proxy_scheduler }}
  syncPeriod: {{ kube_proxy_sync_period }}
  strictARP: {{ kube_proxy_strict_arp }}

Proposed:

ipvs:
  excludeCIDRs: {{ kube_proxy_exclude_cidrs }}
  minSyncPeriod: {{ kube_proxy_min_sync_period }}
  scheduler: {{ kube_proxy_scheduler }}
  syncPeriod: {{ kube_proxy_sync_period }}
  strictARP: {{ kube_proxy_strict_arp }}
  tcpTimeout: {{ kube_proxy_tcp_timeout }}
  tcpFinTimeout: {{ kube_proxy_tcp_fin_timeout }}
  udpTimeout: {{ kube_proxy_udp_timeout }}

Why is this needed:

  • Currently IPVS timeouts has to be configured manually with ipvsadm and the settings are lost on restart.
@fulii fulii added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant