lnmch/kops-arm64
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

#72 fix docs (client-side certs are now supported via kubeconfig)

Browse Source
This commit is contained in:
Henning Jacobs
2017-01-15 18:46:34 +01:00
parent 5dc172e2fa
commit c63d4dcfde
2 changed files with 16 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.rst
View File

@@ -108,11 +108,11 @@ The provided ``Makefile`` will generate a Docker image by default:
Multiple Clusters Multiple Clusters
================= =================
Multiple clusters are supported by passing a list of API server URLs in the ``CLUSTERS`` environment variable. Multiple clusters are supported by passing a list of API servers, reading a kubeconfig file or pointing to an HTTP Cluster Registry endpoint.
These can either be unprotected ``localhost`` URLs or OAuth 2 protected API endpoints.
Note that authentication via client-certificates is currently not supported!
The needed OAuth credentials (``Bearer`` access token) must be provided via a file ``${CREDENTIALS_DIR}/read-only-token``. See the `documentation on multiple clusters`_ for details.
.. _documentation on multiple clusters: https://kubernetes-operational-view.readthedocs.io/en/latest/multiple-clusters.html
Configuration Configuration

12
docs/multiple-clusters.rst
View File

@@ -2,8 +2,18 @@
Multiple Clusters Multiple Clusters
================= =================
Multiple clusters are supported by either passing a static list of API server URLs, using an existing kubeconfig file or pointing to a Cluster Registry HTTP endpoint.
Static List of API Server URLs
==============================
Set the ``CLUSTERS`` environment variable to a comma separated list of Kubernetes API server URLs. Set the ``CLUSTERS`` environment variable to a comma separated list of Kubernetes API server URLs.
These can either be unprotected ``localhost`` URLs or OAuth 2 protected API endpoints.
The needed OAuth credentials (``Bearer`` access token) must be provided via a file ``${CREDENTIALS_DIR}/read-only-token-secret``.
Kubeconfig File Kubeconfig File
=============== ===============
@@ -78,4 +88,6 @@ Example:
$ token=mysecrettoken $ token=mysecrettoken
$ docker run -it -p 8080:8080 -e OAUTH2_ACCESS_TOKENS=read-only=$token hjacobs/kube-ops-view --cluster-registry-url=https://cluster-registry.example.org $ docker run -it -p 8080:8080 -e OAUTH2_ACCESS_TOKENS=read-only=$token hjacobs/kube-ops-view --cluster-registry-url=https://cluster-registry.example.org
Otherwise the needed OAuth credentials (``Bearer`` access token) must be provided via a file ``${CREDENTIALS_DIR}/read-only-token-secret``.
.. _kubeconfig file: https://kubernetes.io/docs/user-guide/kubeconfig-file/ .. _kubeconfig file: https://kubernetes.io/docs/user-guide/kubeconfig-file/