option kube-proxy flag --conntrack-max-per-core #216

Open
rimusz opened this Issue Feb 20, 2017 · 1 comment

Comments

2 participants

rimusz commented Feb 20, 2017

option kube-proxy flag --conntrack-max-per-core support in charm would be good to have, it is specially is needed for web facing apps which use a lot of DNS.

Collaborator

chuckbutler commented Feb 21, 2017

I've seen some cases elsewhere, where the conntrack table is filled from horizontally scaled DNS pods + a high volume of requests. This would be a welcome tunable option.

@wwwtyro wwwtyro added this to Feature Request in CDK Jan 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment