This is a huge step up, but it's still hard for applications to declare that they want configurations like this. We used to ship @quayio on prem with a container that tried to sysctl somaxcon if you ran it as privileged -- non-ideal, but it worked.
This is awesome. I've been looking forward to this for a long time. A number of networking-intensive workloads need to tune sysctls for peak performance. This will provide a declarative way to express that.https://twitter.com/vicnastea/status/1283808664944427009 …
-
-
-
There are tradeoffs. I would factor that into an initContainer, which is similar to what we did in Borg for a long time. Some sysctls can be specified in pod spec (https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/ …), but this couples the app and the OS. We're missing something like StorageClass for nodes.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.