diff options
| author | Ed Costello <epc@epcostello.com> | 2015-07-12 22:03:06 -0400 |
|---|---|---|
| committer | Ed Costello <epc@epcostello.com> | 2015-07-12 22:03:06 -0400 |
| commit | b4deb49a719e9d5c7ece5c930dec4ff225409466 (patch) | |
| tree | cca40e2b45d8668ea17ca81ce2d4b30963463f1f | |
| parent | ee97e734b55c5f605944bcc4e324bdc09bd4c476 (diff) | |
Copy edits for typos
| -rw-r--r-- | networking.md | 2 | ||||
| -rw-r--r-- | security.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/networking.md b/networking.md index af64ed8d..210d10e5 100644 --- a/networking.md +++ b/networking.md @@ -128,7 +128,7 @@ to serve the purpose outside of GCE. The [service](../services.md) abstraction provides a way to group pods under a common access policy (e.g. load-balanced). The implementation of this creates a -virtual IP which clients can access and which is transparantly proxied to the +virtual IP which clients can access and which is transparently proxied to the pods in a Service. Each node runs a kube-proxy process which programs `iptables` rules to trap access to service IPs and redirect them to the correct backends. This provides a highly-available load-balancing solution with low diff --git a/security.md b/security.md index 4ea7d755..c2fd092e 100644 --- a/security.md +++ b/security.md @@ -78,7 +78,7 @@ A pod runs in a *security context* under a *service account* that is defined by 5. Developers should be able to run their own images or images from the community and expect those images to run correctly 6. Developers may need to ensure their images work within higher security requirements specified by administrators 7. When available, Linux kernel user namespaces can be used to ensure 5.2 and 5.4 are met. - 8. When application developers want to share filesytem data via distributed filesystems, the Unix user ids on those filesystems must be consistent across different container processes + 8. When application developers want to share filesystem data via distributed filesystems, the Unix user ids on those filesystems must be consistent across different container processes 6. Developers should be able to define [secrets](secrets.md) that are automatically added to the containers when pods are run 1. Secrets are files injected into the container whose values should not be displayed within a pod. Examples: 1. An SSH private key for git cloning remote data |