1c1da2af04
With openshift/machine-config-operator#3676 we removed globally setting ip forwarding in MCO. We should not be setting it in the default profile for OpenShift. We now set it on a per interface basis as needed. However, by setting proc/sys/net/ipv4/forward rather than (forwarding) it will reset all the values: "This variable is special, its change resets all configuration parameters to their default state (RFC1122 for hosts, RFC1812 for routers)" We suspect this causes upgrade to fail. NTO sets this to 1, which then resets all the per interface config that OVNK wrote. Then during upgrade when there is a tuned profile change, the config change is rolled back so forward is 0, and now there is no connectivity to kapi and upgrade fails. Signed-off-by: Tim Rozet <trozet@redhat.com>
36 lines
897 B
Text
36 lines
897 B
Text
#
|
|
# tuned configuration
|
|
#
|
|
|
|
[main]
|
|
summary=Optimize systems running OpenShift (parent profile)
|
|
include=${f:virt_check:virtual-guest:throughput-performance}
|
|
|
|
[selinux]
|
|
avc_cache_threshold=8192
|
|
|
|
[net]
|
|
nf_conntrack_hashsize=1048576
|
|
|
|
[sysctl]
|
|
kernel.pid_max=>4194304
|
|
fs.aio-max-nr=>1048576
|
|
net.netfilter.nf_conntrack_max=1048576
|
|
net.ipv4.conf.all.arp_announce=2
|
|
net.ipv4.neigh.default.gc_thresh1=8192
|
|
net.ipv4.neigh.default.gc_thresh2=32768
|
|
net.ipv4.neigh.default.gc_thresh3=65536
|
|
net.ipv6.neigh.default.gc_thresh1=8192
|
|
net.ipv6.neigh.default.gc_thresh2=32768
|
|
net.ipv6.neigh.default.gc_thresh3=65536
|
|
vm.max_map_count=262144
|
|
|
|
[sysfs]
|
|
/sys/module/nvme_core/parameters/io_timeout=4294967295
|
|
/sys/module/nvme_core/parameters/max_retries=10
|
|
|
|
[scheduler]
|
|
# see rhbz#1979352; exclude containers from aligning to house keeping CPUs
|
|
cgroup_ps_blacklist=/kubepods\.slice/
|
|
# workaround for rhbz#1921738
|
|
runtime=0
|