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

deprecate DenyExecOnPrivileged/DenyEscalatingExec (#12152)

Browse Source
This commit is contained in:
Jordan Liggitt
2019-02-17 11:07:05 -05:00
committed by Kubernetes Prow Robot
parent 64fc415cdd
commit 079a91fe79
2 changed files with 13 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/blog/_posts/2016-08-00-Security-Best-Practices-Kubernetes-Deployment.md
+2
View File
@@ -4,6 +4,8 @@ date: 2016-08-31
slug: security-best-practices-kubernetes-deployment
url: /blog/2016/08/Security-Best-Practices-Kubernetes-Deployment
---
_Note: some of the recommendations in this post are no longer current. Current cluster hardening options are described in this [documentation](https://kubernetes.io/docs/tasks/administer-cluster/securing-a-cluster/)._
_Editor’s note: today’s post is by Amir Jerbi and Michael Cherny of Aqua Security, describing security best practices for Kubernetes deployments, based on data they’ve collected from various use-cases seen in both on-premises and cloud deployments._
Kubernetes provides many controls that can greatly improve your application security. Configuring them requires intimate knowledge with Kubernetes and the deployment’s security requirements. The best practices we highlight here are aligned to the container lifecycle: build, ship and run, and are specifically tailored to Kubernetes deployments. We adopted these best practices in [our own SaaS deployment](http://blog.aquasec.com/running-a-security-service-in-google-cloud-real-world-example) that runs Kubernetes on Google Cloud Platform.