From fb373d050b8b58440aa658c44d8191985f37d6bf Mon Sep 17 00:00:00 2001 From: Zichang Lin Date: Sat, 19 Sep 2015 14:14:43 +0800 Subject: [PATCH] Fix document link --- examples/guestbook/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/guestbook/README.md b/examples/guestbook/README.md index 9554e023aba..2cfb1c34d37 100644 --- a/examples/guestbook/README.md +++ b/examples/guestbook/README.md @@ -577,7 +577,7 @@ redis-slave 10.0.21.92 6379/TCP app-redis,rol You'll want to set up your guestbook service so that it can be accessed from outside of the internal Kubernetes network. Above, we introduced one way to do that, using the `type: LoadBalancer` spec. -More generally, Kubernetes supports two ways of exposing a service onto an external IP address: `NodePort`s and `LoadBalancer`s , as described [here](../../docs/user-guide/services.md#external-services). +More generally, Kubernetes supports two ways of exposing a service onto an external IP address: `NodePort`s and `LoadBalancer`s , as described [here](../../docs/user-guide/services.md#publishing-services---service-types). If the `LoadBalancer` specification is used, it can take a short period for an external IP to show up in `kubectl get services` output, but you should shortly see it listed as well, e.g. like this: