set net.ipv4.tcp_keepalive_time and net.core.somaxconn for tidb and tikv in init container

Question

What problem does this PR solve?

fix https://github.com/pingcap/tidb-operator/issues/880 for GCP and Alibaba

What is changed and how does it work?

Set net.ipv4.tcpkeepalivetime and net.core.somaxconn for tidb in init container Set net.core.somaxconn for tikv in init container

Check List

Tests

• Unit test
• Manual test (add detailed scripts or steps below)

Code changes

• Has Helm charts change
• Has Go code change
• Has documents change

Related changes - Need to update the documentation

Does this PR introduce a user-facing change?:

release-note
Support configuring net.ipv4.tcp<em>keepalive</em>time and net.core.somaxconn for TiDB and configuring net.core.somaxconn for TiKV.
 

Answer 1

After discussion with and , will update the solution as below:

• users still configure PodSecurityContext.sysctls in values.yaml
• if annotations for init container is set in values.yaml, tidb-operator will convert PodSecurityContext.sysctl to init container;
• otherwise, set PodSecurityContext with existing logic.