From 527682ca66941a19dd078c9af1b503b5d88189b4 Mon Sep 17 00:00:00 2001 From: Stewart-YU Date: Tue, 22 Aug 2017 09:21:03 +0800 Subject: [PATCH 1/2] Update access-cluster.md Missing signals. --- docs/tasks/access-application-cluster/access-cluster.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tasks/access-application-cluster/access-cluster.md b/docs/tasks/access-application-cluster/access-cluster.md index b0b38955fe..09525c6fc0 100644 --- a/docs/tasks/access-application-cluster/access-cluster.md +++ b/docs/tasks/access-application-cluster/access-cluster.md @@ -134,7 +134,7 @@ If the application is deployed as a Pod in the cluster, please refer to the [nex #### Python client -To use [Python client](https://github.com/kubernetes-incubator/client-python), run the following command: `pip install kubernetes` See [Python Client Library page](https://github.com/kubernetes-incubator/client-python) for more installation options. +To use [Python client](https://github.com/kubernetes-incubator/client-python), run the following command: `pip install kubernetes`. See [Python Client Library page](https://github.com/kubernetes-incubator/client-python) for more installation options. The Python client can use the same [kubeconfig file](/docs/user-guide/kubeconfig-file) as the kubectl CLI does to locate and authenticate to the apiserver. See this [example](https://github.com/kubernetes-incubator/client-python/tree/master/examples/example1.py). @@ -235,7 +235,7 @@ $ kubectl cluster-info This shows the proxy-verb URL for accessing each service. For example, this cluster has cluster-level logging enabled (using Elasticsearch), which can be reached -at `https://104.197.5.247/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/` if suitable credentials are passed, or through a kubectl proxy at, for example: +at `https://104.197.5.247/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/`. If suitable credentials are passed, or through a kubectl proxy at, for example: `http://localhost:8080/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/`. (See [above](#accessing-the-cluster-api) for how to pass credentials or use kubectl proxy.) From 4e3cfc94faf2a452be87500bf22944a3db2582c6 Mon Sep 17 00:00:00 2001 From: Jennifer Rondeau Date: Tue, 22 Aug 2017 18:29:05 -0400 Subject: [PATCH 2/2] Update access-cluster.md Fix one addition in original PR (added period is incorrect at l238). Rewrote the paragraph for greater clarity, however. --- docs/tasks/access-application-cluster/access-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/access-application-cluster/access-cluster.md b/docs/tasks/access-application-cluster/access-cluster.md index 09525c6fc0..bee827e8c8 100644 --- a/docs/tasks/access-application-cluster/access-cluster.md +++ b/docs/tasks/access-application-cluster/access-cluster.md @@ -235,7 +235,7 @@ $ kubectl cluster-info This shows the proxy-verb URL for accessing each service. For example, this cluster has cluster-level logging enabled (using Elasticsearch), which can be reached -at `https://104.197.5.247/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/`. If suitable credentials are passed, or through a kubectl proxy at, for example: +at `https://104.197.5.247/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/` if suitable credentials are passed. Logging can also be reached through a kubectl proxy, for example at: `http://localhost:8080/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/`. (See [above](#accessing-the-cluster-api) for how to pass credentials or use kubectl proxy.)