From df85b7711b63e7dbcdea0351a74111d34d6ed633 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 19 Jul 2018 17:46:35 -0700 Subject: [PATCH] service discovery high level --- content/rancher/v2.x/en/kubernetes-in-rancher/_index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/_index.md index beffbfbb447..b65195b808e 100644 --- a/content/rancher/v2.x/en/kubernetes-in-rancher/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/_index.md @@ -123,6 +123,10 @@ For more information, see [Ingress]({{< baseurl >}}/rancher/v2.x/en/kubernetes-i ## Service Discovery +After you expose your cluster to external requests using a load balancer and/or ingress, it's only available by IP address. To create a resolveable hostname, you must create a Service Record, which is record that maps a IP address, external hostname, DNS record alias, workloads, or labled pods to a specific hostname. + +For more information, see [Service Discovery]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/service-discovery). + ## Volumes and Storage For workloads that need to retain their state, you must add external storage for the workload. Storage volumes are locations outside your of your pods where applications can store their data. Because the storage is external to the workload, if a container fails, the container that replaces it can restore the external data, making recovery appear seamless.