diff --git a/docs/multiple-clusters.rst b/docs/multiple-clusters.rst
index 404fdb5..73d8267 100644
--- a/docs/multiple-clusters.rst
+++ b/docs/multiple-clusters.rst
@@ -4,6 +4,46 @@ Multiple Clusters
 
 Set the ``CLUSTERS`` environment variable to a comma separated list of Kubernetes API server URLs.
 
+Kubeconfig File
+===============
+
+The `kubeconfig file`_ allows defining multiple cluster contexts with potential different authentication mechanisms.
+
+Kubernetes Operational View will try to reach all defined contexts when given the ``--kubeconfig-path`` command line option (or ``KUBECONFIG_PATH`` environment variable).
+
+Example:
+
+Assuming ``~/.kube/config`` as the following contents with two defined contexts:
+
+.. code-block:: yaml
+
+    apiVersion: v1
+    kind: Config
+    clusters:
+    - cluster: {server: 'https://kube.foo.example.org'}
+      name: kube_foo_example_org
+    - cluster: {server: 'https://kube.bar.example.org'}
+      name: kube_bar_example_org
+    contexts:
+    - context: {cluster: kube_foo_example_org, user: kube_foo_example_org}
+      name: kube_foo_example_org
+    - context: {cluster: kube_bar_example_org, user: kube_bar_example_org}
+      name: kube_bar_example_org
+    current-context: kube_foo_example_org
+    users:
+    - name: kube_foo_example_org
+      user: {token: myfootoken123}
+    - name: kube_bar_example_org
+      user: {token: mybartoken456}
+
+Kubernetes Operational View would try to reach both endpoints with the respective token for authentication:
+
+.. code-block:: bash
+
+    $ # note that we need to mount the local ~/.kube/config file into the Docker container
+    $ docker run -it -p 8080:8080 -v ~/.kube/config:/kubeconfig hjacobs/kube-ops-view --kubeconfig-path=/kubeconfig
+
+
 Cluster Registry
 ================
 
@@ -22,10 +62,12 @@ Set either the ``CLUSTER_REGISTRY_URL`` environment variable or the ``--cluster-
         ]
     }
 
-The cluster registry will be queryied with an OAuth Bearer token, the token can be statically set via the ``OAUTH2_ACCESS_TOKENS`` environment variable.
+The cluster registry will be queried with an OAuth Bearer token, the token can be statically set via the ``OAUTH2_ACCESS_TOKENS`` environment variable.
 Example:
 
 .. code-block:: bash
 
     $ 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
+
+.. _kubeconfig file: https://kubernetes.io/docs/user-guide/kubeconfig-file/