From a9cf28f620a735145c0d2e87b51d9c5015dd10f9 Mon Sep 17 00:00:00 2001 From: "ashish.billore" Date: Sat, 27 May 2017 14:12:45 +0900 Subject: [PATCH] Update link to k8s doc and minor formatting Updated the external link to k8s loadbalancer. Original link does 404 and then redirects leaving on the broad topics of services in k8s. Also, minor readability formatting done. Closes-Bug: #1692802 Change-Id: I22336a6f2b9319e42593db600e88d82c0e60bfff --- doc/source/dev/kubernetes-load-balancer.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/source/dev/kubernetes-load-balancer.rst b/doc/source/dev/kubernetes-load-balancer.rst index c744393c7a..dc9e28791f 100644 --- a/doc/source/dev/kubernetes-load-balancer.rst +++ b/doc/source/dev/kubernetes-load-balancer.rst @@ -20,9 +20,8 @@ in the service manifest. When the service is created, Kubernetes will add an external load balancer in front of the service so that the service will have an external IP address in addition to the internal IP address on the container network. The service endpoint can then be accessed with this external IP -address. Refer to the Kubernetes guide for more details:: - - http://kubernetes.io/v1.0/docs/user-guide/services.html#external-services +address. Refer to the `Kubernetes service document `_ for more details. A Kubernetes cluster deployed by Magnum will have all the necessary configuration required for the external load balancer. This document describes @@ -133,9 +132,10 @@ Create a file (e.g nginx-service.yaml) describing a service for the nginx pod:: app: nginx type: LoadBalancer -Assuming that a Kubernetes cluster named k8sclusterv1 has been created, deploy -the pod and service by the commands. Please refer to the quickstart guide on -how to connect to Kubernetes running on the launched cluster.:: +Please refer to the `quickstart `_ guide on how to connect to Kubernetes running on the launched +cluster. Assuming a Kubernetes cluster named k8sclusterv1 has been created, +deploy the pod and service using following commands:: kubectl create -f nginx.yaml @@ -283,8 +283,8 @@ For the VIP of the pool:: Note that the VIP is created on the private network of the cluster; therefore it has an internal IP address of 10.0.0.7. This address is also associated as -the "external address" of the Kubernetes service. You can verify in Kubernetes -by running the kubectl command:: +the "external address" of the Kubernetes service. You can verify this in +Kubernetes by running following command:: kubectl get services NAME LABELS SELECTOR IP(S) PORT(S)