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

securing a cluster: add recommendations about cloud metadata APIs (#6659)

Browse Source
This commit is contained in:
Eric Chiang
2018-01-08 14:52:12 -08:00
committed by Steve Perry
parent b9b39f28db
commit 77d08557d7
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/administer-cluster/securing-a-cluster.md
+10
View File
@@ -128,6 +128,16 @@ Additional protections may be available that control network rules on a per plug
environment basis, such as per-node firewalls, physically separating cluster nodes to environment basis, such as per-node firewalls, physically separating cluster nodes to
prevent cross talk, or advanced networking policy. prevent cross talk, or advanced networking policy.
### Restricting cloud metadata API access
Cloud platforms (AWS, Azure, GCE, etc.) often expose metadata services locally to instances.
By default these APIs are accessible by pods running on an instance and can contain cloud
credentials for that node, or provisioning data such as kubelet credentials. These credentials
can be used to escalate within the cluster or to other cloud services under the same account.
When running Kubernetes on a cloud platform limit permissions given to instance credentials, use
[network policies](/docs/tasks/administer-cluster/declare-network-policy/) to restrict pod access
to the metadata API, and avoid using provisioning data to deliver secrets.
### Controlling which nodes pods may access ### Controlling which nodes pods may access