Add reference to apiserver-host flag

docs/troubleshooting.md

@@ -31,9 +31,12 @@ The Ingress controller needs information from apiserver. Therefore, authenticati
 
 1. _Service Account:_ This is recommended, because nothing has to be configured. The Ingress controller will use information provided by the system to communicate with the API server. See 'Service Account' section for details.
 
-2. _Kubeconfig file:_ In some Kubernetes environments service accounts are not available. In this case a manual configuration is required. The Ingress controller binary can be started with the `--kubeconfig` flag. The value of the flag is a path to a file specifying how to connect to the API server.
+2. _Kubeconfig file:_ In some Kubernetes environments service accounts are not available. In this case a manual configuration is required. The Ingress controller binary can be started with the `--kubeconfig` flag. The value of the flag is a path to a file specifying how to connect to the API server. Using the `--kubeconfig` does not requires the flag `--apiserver-host`.
 The format of the file is identical to `~/.kube/config` which is used by kubectl to connect to the API server. See 'kubeconfig' section for details.
 
+3. _Using the flag `--apiserver-host`:_ Using this flag `--apiserver-host=http://localhost:8080` it is possible to specify an unsecure api server or reach a remote kubernetes cluster using [kubectl proxy](https://kubernetes.io/docs/user-guide/kubectl/kubectl_proxy/).
+Please do not use this approach in production.
+
 In the diagram below you can see the full authentication flow with all options, starting with the browser
 on the lower left hand side.
 ```
@@ -155,6 +158,7 @@ If you want to use a kubeconfig file for authentication, create a deployment fil
 
 *Note:* the important part is the flag `--kubeconfig=/etc/kubernetes/kubeconfig.yaml`.
 
+
 ```
 kind: Service
 apiVersion: v1