2 ms·
Given the additional context “we need out k8s deployment to work for customers who use selinux on their nodes”, the motivation to do this makes more sense. The
by pm90 6y ago
Given the additional context “we need out k8s deployment to work for customers who use selinux on their nodes”, the motivation to do this makes more sense. The majority of k8s users likely don’t share their clusters with untrusted/low trust users so it seems unlikely to help them much.
Not to dunk on the work you’ve done: it’s still awesome. Just want to point out the disconnect from users wondering how this would help them.
- kevin_nisbet 6y agoWe do try and point this out in the article itself, but apparently failed to convey the total context by trying not to spend a lot of time explaining gravity, which for the particular article shouldn't be that important. > The problem we had was that Gravity was never designed to run on SELinux-enabled hosts and our customers kept randomly breaking their installations when trying to run Gravity with SELinux enabled.
- jandrewrogers 6y agoI think this misrepresents the use case. Most customers that require k8s on SELinux don't share their clusters with untrusted users. It provides much stronger isolation between containers in the case that one is compromised, reducing the scope of damage when a system is successfully attacked. In other words, they don't assume that a trusted container/user stays "trusted" operationally.