Viktor Kuzmin

Same for me. I'm a sponsor now :) Also going to try to join development.

Personally I don't think that sticking to network drives are good idea. We're using kubernetes with local storage mostly, cause it is much more faster.

Generally there can be two types of volumes. First one - create PVC for all pods created during build and this PVC can be RWX (and network) and second one...

> @kvaster This does not work for data that has to be shared across pods (because they can be located on different nodes) and even if you host them all...

I've adjust limits very big values, but I still get 'Too many open files' error :( Seems that it's another reason...

Also have one question: why [k8s-views-nodes.json](https://github.com/dotdc/grafana-dashboards-kubernetes/blob/master/dashboards/k8s-views-nodes.json) and [k8s-system-api-server.json](https://github.com/dotdc/grafana-dashboards-kubernetes/blob/master/dashboards/k8s-system-api-server.json) were excluded ? Is there any reason for this ?

Any comments ?

Attaching my first attempt to fix this problem by myself. This is ipv4 only. This patch is for 1.13.7. With 1.14.2 it is the same, but it doesn't work with...

It seems that this patch works only for 'Legacy' host routing and does not work for 'BPF' host routing.

@brb, I have socket LB enabled: ``` k8sServiceHost: 10.117.12.100 nodePort: directRoutingDevice: wan0.4000 devices: wan+ containerRuntime: integration: auto pmtuDiscovery: enabled: true nodeport: enabled: true k8sServicePort: 6443 kubeProxyReplacement: true ipv4NativeRoutingCIDR: 10.244.0.0/16 masquerade:...