From f326993ce425441fa599fbf6e47e99cd664dd9d7 Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Tue, 28 Mar 2017 18:56:45 +0800 Subject: [PATCH] update invalid links update invalid links --- docs/user-guide/services/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/user-guide/services/index.md b/docs/user-guide/services/index.md index e2890df2cd..eb07299b35 100644 --- a/docs/user-guide/services/index.md +++ b/docs/user-guide/services/index.md @@ -19,7 +19,7 @@ Enter `Services`. A Kubernetes `Service` is an abstraction which defines a logical set of `Pods` and a policy by which to access them - sometimes called a micro-service. The set of `Pods` targeted by a `Service` is (usually) determined by a [`Label -Selector`](/docs/user-guide/labels/#label-selectors) (see below for why you might want a +Selector`](/docs/concepts/overview/working-with-objects/labels/#label-selectors) (see below for why you might want a `Service` without a selector). As an example, consider an image-processing backend which is running with 3 @@ -345,7 +345,7 @@ can do a DNS SRV query for `"_http._tcp.my-service.my-ns"` to discover the port number for `"http"`. The Kubernetes DNS server is the only way to access services of type -`ExternalName`. More information is available in the [DNS Admin Guide](http://kubernetes.io/docs/admin/dns/). +`ExternalName`. More information is available in the [DNS Pods and Services](/docs/concepts/services-networking/dns-pod-service/). ## Headless services @@ -661,4 +661,4 @@ object](/docs/api-reference/v1/definitions/#_v1_service). ## For More Information -Read [Service Operations](/docs/user-guide/services/operations/). +Read [Connecting a Front End to a Back End Using a Service](/docs/tutorials/connecting-apps/connecting-frontend-backend/).