diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2019-03-08 09:29:26 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-03-08 09:29:26 -0800 |
| commit | 3fc806d3ff6b9f07ff1253fb5c21e15f7ad01e7a (patch) | |
| tree | b168bb07b030a9a3497e7066cbb13767a7cf4c0d | |
| parent | 1eef1b3f899f262f676e20c371db1137cdd638f1 (diff) | |
| parent | b4eae4efd565b219333ca0894da442c9d759891f (diff) | |
Merge pull request #3218 from knightXun/patch-3
replace proxy with kube-proxy
| -rw-r--r-- | contributors/design-proposals/auth/security.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/contributors/design-proposals/auth/security.md b/contributors/design-proposals/auth/security.md index 846b2c39..d2c3e0e2 100644 --- a/contributors/design-proposals/auth/security.md +++ b/contributors/design-proposals/auth/security.md @@ -181,13 +181,13 @@ An administrator must be able to properly secure Kubernetes at a policy level, rather than at an implementation level, and schema changes over time should not risk unintended security leaks. -Both the Kubelet and Kube Proxy need information related to their specific roles - -for the Kubelet, the set of pods it should be running, and for the Proxy, the -set of services and endpoints to load balance. The Kubelet also needs to provide +Both the kubelet and kube-proxy need information related to their specific roles - +for the kubelet, the set of pods it should be running, and for the kube-proxy, the +set of services and endpoints to load balance. The kubelet also needs to provide information about running pods and historical termination data. The access -pattern for both Kubelet and Proxy to load their configuration is an efficient -"wait for changes" request over HTTP. It should be possible to limit the Kubelet -and Proxy to only access the information they need to perform their roles and no +pattern for both kubelet and kube-proxy to load their configuration is an efficient +"wait for changes" request over HTTP. It should be possible to limit the kubelet +and kube-proxy to only access the information they need to perform their roles and no more. The controller manager for Replication Controllers and other future controllers |