diff options
| author | Tim Hockin <thockin@google.com> | 2015-05-23 13:41:11 -0700 |
|---|---|---|
| committer | Tim Hockin <thockin@google.com> | 2015-05-28 16:10:44 -0700 |
| commit | f21879b3d766d7c89983e429f3ee068bf73854d5 (patch) | |
| tree | 6852476c51780a09abff0180c662d67c82377aaa | |
| parent | 68ae206a68d52babea39f37b7c9b5a8b5ea0523e (diff) | |
Rename 'portal IP' to 'cluster IP' most everywhere
This covers obvious transforms, but not --portal_net, $PORTAL_NET and
similar.
| -rw-r--r-- | autoscaling.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/autoscaling.md b/autoscaling.md index 29d20c82..31374448 100644 --- a/autoscaling.md +++ b/autoscaling.md @@ -42,7 +42,7 @@ applications will expose one or more network endpoints for clients to connect to balanced or situated behind a proxy - the data from those proxies and load balancers can be used to estimate client to server traffic for applications. This is the primary, but not sole, source of data for making decisions. -Within Kubernetes a [kube proxy](http://docs.k8s.io/services.md#ips-and-portals) +Within Kubernetes a [kube proxy](http://docs.k8s.io/services.md#ips-and-vips) running on each node directs service requests to the underlying implementation. While the proxy provides internal inter-pod connections, there will be L3 and L7 proxies and load balancers that manage |