Lock down host OS leaks through container barrier #351
Labels
bug
Something isn't working
c/k8s
Kubernetes component
c/node
Issues related to low-level node services and startup
unfortunate
Things which we wouldn't implement in an ideal world.
There are some unfortunate abstraction leaks through the container boundary, for example mount attributes (noexec, nosuid, ...) and things like device permissions. We should lock these down and test for that as these are essentially ABI for us. Even a slight change can easily break customer workloads.
The text was updated successfully, but these errors were encountered: