Change:
} ``` <del> You can provide a suffix and parameters: </del> <ins> #### Using web browsers In a web browser, navigate to the proxy URL and then enter your username and password when prompted. For example, you would copy and paste the following proxy URL into the address bar of your browser: </ins> ``` <del> $ curl -k -u admin:4mty0Vl9nNFfwLJz https://104.197.5.247/api/v1beta3/proxy/namespaces/default/services/elasticsearch-logging/_cluster/health?pretty=true { "cluster_name" : "kubernetes_logging", "status" : "yellow", "timed_out" : false, "number_of_nodes" : 1, "number_of_data_nodes" : 1, "active_primary_shards" : 5, "active_shards" : 5, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 5 } </del> <ins> https://104.197.5.247/api/v1beta3/proxy/namespaces/default/services/elasticsearch-logging/ </ins> ``` <del> You can also visit the endpoint of a service via the proxy URL e.g. ``` https://104.197.5.247/api/v1beta3/proxy/namespaces/default/services/kibana-logging ``` The first time you access the cluster using a proxy address from a browser you will be prompted for a username and password which can also be found in the `User` and `Password` fields of the `kubernetes_auth` file. ## Redirect A `redirect` request on a service will return a HTTP redirect response which identifies a specific node that can handle the request. Since the hostname that is returned is usually only accessible from inside the cluster this feature is useful only for code running inside the cluster. Subsequent `redirect` calls to the same resource may return different results e.g. when the service picks different replica nodes to serve the request. This feature can be useful to short circuit calls to the proxy server by obtaining the address of a node on the cluster which can be used for further requests which do not involve the proxy server. For example, the query below is run on a GCE virtual machine `oban` that is running in the same project and GCE default network as the Kubernetes cluster. The `-L` flag tells curl to follow the redirect information returned by the redirect call. </del> <ins> ## <a name="redirect"></a>Requesting redirects Use a `redirect` request so that the server returns an HTTP redirect response and identifies the specific node and service that can handle the request. **Note**: Since the hostname or address that is returned is usually only accessible from inside the cluster, sending `redirect` requests is useful only for code running inside the cluster. Also, keep in mind that any subsequent `redirect` requests to the same server might return different results (because another node at that point in time can better serve the request). **Tip**: Use a redirect request to reduce calls to the proxy server by first obtaining the address of a node on the cluster and then using that returned address for all subsequent requests. ##### Example To request a redirect and then verify the address that gets returned, let's run a query on `oban` (Google Compute Engine virtual machine). Note that `oban` is running in the same project and default network (Google Compute Engine) as the Kubernetes cluster. To request a redirect for the Elasticsearch service, we can run the following `curl` command: </ins> ``` <del> user@oban:~$ curl -L -k -u admin:4mty0Vl9nNFfwLJz https://104.197.5.247/api/v1beta3/redirect/namespaces/default/services/elasticsearch-logging </del> <ins> user@oban:~$ curl -L -k -u admin:4mty0Vl9nNFfwLJz https://104.197.5.247/api/v1beta3/redirect/namespaces/default/services/elasticsearch-logging/ </ins> { "status" : 200, "name" : "Skin",

Discussion:
is out of date. Please update for the current location/contents of the file and v1beta3. Once is submitted we should also update the examples to show to to curl using bearer tokens instead of basic auth credentials.
We're working on scrubbing the docs and examples of references to v1beta1 () prior to deleting that API, so it would be good to have this in soon.
: let me know if you want to punt this back to me -- now that I have some clue again about how to access an cluster (assuming I can create a cluster!).
Punting back to you. Getting the auth credentials is accomplished via But I think you have a better idea how to curl with token auth than I do.