Closed acrogenesis closed 1 year ago
I think something like this would solve it. https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/
apiVersion: v1
kind: Pod
metadata:
name: sysctl-example
spec:
securityContext:
sysctls:
- name: net.core.rmem_max
value: "2500000"
...
All unsafe sysctls are disabled by default and must be allowed manually by the cluster admin on a per-node basis. Pods with disabled unsafe sysctls will be scheduled, but will fail to launch.
Here they refer to one of the net.core.* sysctls as unsafe and should be enabled per node by passing it to the kubelet argument list? Looks like it might not be that straightforward. Did doing the above manually on the deployment work for you?
I get this warning when cloudflared starts
https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size