whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix links about apiserver proxy

Browse Source 
* The link in access-cluster.md is stale
* service name segment of apiserver proxy must have trailing colon when
  schema is specified
* Replace apiserver address with a reserved documentation IP address

Signed-off-by: Quan Tian <qtian@vmware.com>
This commit is contained in:
Quan Tian
2022-05-18 11:59:07 +08:00
parent dab4e5d146
commit 56e597ced4
2 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/access-application-cluster/access-cluster-services.md
+10 -10
View File
@@ -64,17 +64,17 @@ kubectl cluster-info
The output is similar to this: The output is similar to this:
``` ```
Kubernetes master is running at https://104.197.5.247 Kubernetes master is running at https://192.0.2.1
elasticsearch-logging is running at https://104.197.5.247/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy elasticsearch-logging is running at https://192.0.2.1/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy
kibana-logging is running at https://104.197.5.247/api/v1/namespaces/kube-system/services/kibana-logging/proxy kibana-logging is running at https://192.0.2.1/api/v1/namespaces/kube-system/services/kibana-logging/proxy
kube-dns is running at https://104.197.5.247/api/v1/namespaces/kube-system/services/kube-dns/proxy kube-dns is running at https://192.0.2.1/api/v1/namespaces/kube-system/services/kube-dns/proxy
grafana is running at https://104.197.5.247/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy grafana is running at https://192.0.2.1/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy
heapster is running at https://104.197.5.247/api/v1/namespaces/kube-system/services/monitoring-heapster/proxy heapster is running at https://192.0.2.1/api/v1/namespaces/kube-system/services/monitoring-heapster/proxy
``` ```
This shows the proxy-verb URL for accessing each service. 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 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://192.0.2.1/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/`. `http://localhost:8080/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/`.
{{< note >}} {{< note >}}
@@ -104,13 +104,13 @@ The supported formats for the `<service_name>` segment of the URL are:
* To access the Elasticsearch service endpoint `_search?q=user:kimchy`, you would use: * To access the Elasticsearch service endpoint `_search?q=user:kimchy`, you would use:
``` ```
http://104.197.5.247/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/_search?q=user:kimchy http://192.0.2.1/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/_search?q=user:kimchy
``` ```
* To access the Elasticsearch cluster health information `_cluster/health?pretty=true`, you would use: * To access the Elasticsearch cluster health information `_cluster/health?pretty=true`, you would use:
``` ```
https://104.197.5.247/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/_cluster/health?pretty=true https://192.0.2.1/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/_cluster/health?pretty=true
``` ```
The health information is similar to this: The health information is similar to this:
@@ -133,7 +133,7 @@ The supported formats for the `<service_name>` segment of the URL are:
* To access the *https* Elasticsearch service health information `_cluster/health?pretty=true`, you would use: * To access the *https* Elasticsearch service health information `_cluster/health?pretty=true`, you would use:
``` ```
https://104.197.5.247/api/v1/namespaces/kube-system/services/https:elasticsearch-logging/proxy/_cluster/health?pretty=true https://192.0.2.1/api/v1/namespaces/kube-system/services/https:elasticsearch-logging:/proxy/_cluster/health?pretty=true
``` ```
#### Using web browsers to access services running on the cluster #### Using web browsers to access services running on the cluster
content/en/docs/tasks/access-application-cluster/access-cluster.md
+1 -1
View File
@@ -233,7 +233,7 @@ There are several different proxies you may encounter when using Kubernetes:
- locates apiserver - locates apiserver
- adds authentication headers - adds authentication headers
1. The [apiserver proxy](#discovering-builtin-services): 1. The [apiserver proxy](/docs/tasks/access-application-cluster/access-cluster-services/#discovering-builtin-services):
- is a bastion built into the apiserver - is a bastion built into the apiserver
- connects a user outside of the cluster to cluster IPs which otherwise might not be reachable - connects a user outside of the cluster to cluster IPs which otherwise might not be reachable