Kernel network tunables need better defaults and to be configurable

Bug #1825436 reported by James Troup
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
Fix Released
Medium
Mike Wilson
Kubernetes Worker Charm
Fix Released
Medium
Mike Wilson

Bug Description

Through bitter experience in OpenStack we've discovered the need to tweak some of Linux's network tunable parameters. I strongly suspect those same parameters need tuned on CDK too.

The OpenStack charms default to the following changes:

      { net.ipv4.neigh.default.gc_thresh1 : 128,
        net.ipv4.neigh.default.gc_thresh2 : 28672,
        net.ipv4.neigh.default.gc_thresh3 : 32768,
        net.ipv6.neigh.default.gc_thresh1 : 128,
        net.ipv6.neigh.default.gc_thresh2 : 28672,
        net.ipv6.neigh.default.gc_thresh3 : 32768,
        net.nf_conntrack_max : 1000000,
        net.netfilter.nf_conntrack_buckets : 204800,
        net.netfilter.nf_conntrack_max : 1000000 }

Others have run into the need to change gc_thresh when running Kubernetes at scale, e.g.:

  https://<email address hidden>/tinders-move-to-kubernetes-cda2a6372f44

And any CDK charm which enables iptables on a host should consider having support for both changing the conntrack settings and have defaults like those above.

Revision history for this message
Tim Van Steenburgh (tvansteenburgh) wrote :
Changed in charm-kubernetes-worker:
status: New → Triaged
importance: Undecided → Medium
Mike Wilson (knobby)
Changed in charm-kubernetes-worker:
assignee: nobody → Mike Wilson (knobby)
Mike Wilson (knobby)
Changed in charm-kubernetes-worker:
status: Triaged → In Progress
Revision history for this message
Mike Wilson (knobby) wrote :
Revision history for this message
Tim Van Steenburgh (tvansteenburgh) wrote :

Will be available in kubernetes-worker-523 and later, and kubernetes-master-661 and later.

Changed in charm-kubernetes-worker:
status: In Progress → Fix Committed
Revision history for this message
George Kraft (cynerva) wrote :
Revision history for this message
George Kraft (cynerva) wrote :

Fix is available in candidate channels:
cs:~containers/kubernetes-master-684
cs:~containers/kubernetes-worker-541

Revision history for this message
George Kraft (cynerva) wrote :

Fix released to stable with these charm revisions:
cs:~containers/kubernetes-master-684
cs:~containers/kubernetes-worker-541

Changed in charm-kubernetes-master:
importance: Undecided → Medium
assignee: nobody → Mike Wilson (knobby)
status: New → Fix Released
Changed in charm-kubernetes-worker:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.