Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container Isolation #46

Open
peterlamar opened this issue Aug 14, 2015 · 3 comments
Open

Container Isolation #46

peterlamar opened this issue Aug 14, 2015 · 3 comments

Comments

@peterlamar
Copy link

As a tenant, my containers are isolated from other containers on the platform so that my workload is secure

@kenjones-cisco
Copy link
Contributor

The nature of the workloads being containerized should solve that, otherwise it would more likely be an issue of resource contention. And that can be managed through limits on PODs, or providing multiple kubernetes clusters.

@altvnk
Copy link
Contributor

altvnk commented Aug 14, 2015

@peterlamar
Copy link
Author

Default Kubernetes has docker running as a root. Compromise your host and you can compromise your VM, hack the network and steal data. At least, thats how I have heard the story.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants