Rewrite docs for accessing the cluster.

Put discussion of how to access the API ahead of discussion about
how to access other services on the cluster.

More clearly distinguish the different kinds of proxies.

Explain pros and cons of different approaches better.

Remove cluster-admin-oriented documentation from user guide.

More links.
This commit is contained in:
Eric Tune
2015-06-05 16:33:57 -07:00
parent 0f1c4c25c3
commit e82b40e64b
4 changed files with 213 additions and 75 deletions

View File

@@ -38,12 +38,11 @@ kubernetes API, or to contribute directly to the kubernetes project.
(e.g. ssh keys, passwords) separately from the Pods that use them, protecting
the sensitive data from proliferation by tools that process pods.
* **Accessing the API and other cluster services via a Proxy** [accessing-the-cluster.md](../docs/accessing-the-cluster.md)
* **API Overview** ([api.md](api.md)): Pointers to API documentation on various topics
and explanation of Kubernetes's approaches to API changes and API versioning.
* **Accessing the API** ([accessing_the_api.md](accessing_the_api.md)):
Ports, IPs, proxies, and firewall rules.
* **Kubernetes Web Interface** ([ui.md](ui.md)): Accessing the Kubernetes
web user interface.
@@ -88,8 +87,6 @@ kubernetes API, or to contribute directly to the kubernetes project.
Provides resource information such as size, type, and quantity to assist in
assigning Kubernetes resources appropriately.
* **Accessing cluster services via a Proxy** [accessing-the-cluster.md](../docs/accessing-the-cluster.md)
* The [API object documentation](http://kubernetes.io/third_party/swagger-ui/).
* Frequently asked questions are answered on this project's [wiki](https://github.com/GoogleCloudPlatform/kubernetes/wiki).