Ensure performance tuning is always applied
Ensure performance tuning is always applied

Previously, with the patch from #43146, it was possible for a
network configured with a single ingress or load balancer on a
distribution which does not have the `ip_vs` kernel module loaded
by default to try to apply sysctls which did not exist yet, and
subsequently dynamically load the module as part of ipvs/netlink.go.

This module is vendored, and not a great place to try to tie back
into core libnetwork functionality, so also ensure that the sysctls
(which are idempotent) are called after ingress/lb creation once
`ipvs` has been initialized.

Signed-off-by: Ryan Barry <3b861f9842bca40b09cc2c02b4184f72757ccc27@mirantis.com>

nawawi/docker,mahak/docker,Mokolea/docker,cpuguy83/docker,nawawi/docker,konstruktoid/docker-upstream,Ramzec/docker,cpuguy83/docker,moby/moby,Mokolea/docker,konstruktoid/docker-upstream,trebonian/docker,cpuguy83/docker,Ramzec/docker,Mokolea/docker,jimjag/docker,jimjag/docker,moul/docker,thaJeztah/docker,moul/docker,jimjag/docker,thaJeztah/docker,nawawi/docker,thaJeztah/docker,trebonian/docker,moul/docker,mahak/docker,konstruktoid/docker-upstream,thaJeztah/docker,moby/moby,nawawi/docker,mahak/docker,Ramzec/docker,Mokolea/docker,mahak/docker,trebonian/docker,trebonian/docker,moby/moby,cpuguy83/docker,jimjag/docker,moul/docker,moby/moby,Ramzec/docker,konstruktoid/docker-upstream