whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #27555 from PushkarJ/patch-1

Browse Source 
Update CNCF security white-paper link
This commit is contained in:
Kubernetes Prow Robot
2021-04-15 03:59:50 -07:00
committed by GitHub
parent 8b122de457 36d5eb8ec8
commit 94b78144ab
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/blog/_posts/2021-04-15-Three-Tenancy-Models-for-Kubernetes.md
+1 -2
View File
@@ -44,7 +44,7 @@ The [Virtual Cluster](https://github.com/kubernetes-sigs/multi-tenancy/tree/mast
## Security considerations
Cloud native security involves different system layers and lifecycle phases as described in the [Cloud Native Security Whitepaper](https://www.cncf.io/blog/2020/11/18/announcing-the-cloud-native-security-white-paper/) from CNCF SIG Security. Without proper security measures implemented across all layers and phases, Kubernetes tenant isolation can be compromised and a security breach with one tenant can threaten other tenants.
Cloud native security involves different system layers and lifecycle phases as described in the [Cloud Native Security Whitepaper](/blog/2020/11/18/cloud-native-security-for-your-clusters) from CNCF SIG Security. Without proper security measures implemented across all layers and phases, Kubernetes tenant isolation can be compromised and a security breach with one tenant can threaten other tenants.
It is important for any new user to Kubernetes to realize that the default installation of a new upstream Kubernetes cluster is not secure, and you are going to need to invest in hardening it in order to avoid security issues.
@@ -78,4 +78,3 @@ The [Kubernetes Multi-Tenancy Working Group](https://github.com/kubernetes-sigs/
If you are interested in multi-tenancy topics, or would like to share your use cases, please join us in an upcoming [community meeting](https://github.com/kubernetes/community/blob/master/wg-multitenancy/README.md) or reach out on the *wg-multitenancy channel* on the [Kubernetes slack](https://slack.k8s.io/).