Merge pull request #812 from garden-io/remote-ingress-update-docs

Remote ingress update docs

docs/using-garden/remote-clusters.md

@@ -6,7 +6,7 @@ Many of the steps are not specific to Garden as such, so you may have already pe
 and/or may need to follow the provided links in each section for details on how to perform the steps you have
 not yet completed.
 
-## Setup 
+## Setup
 
 ### Connecting to the cluster
 
@@ -33,7 +33,7 @@ project:
 
 ### Ingress, TLS and DNS
 
-The cluster needs to have a configured [nginx ingress controller](https://github.com/kubernetes/ingress-nginx).
+By default, Garden will not install an ingress controller for remote environments. This can be toggled by setting the [`setupIngressController` flag](../reference/providers/kubernetes#environments.providers.setupingresscontroller) to `nginx`. Alternatively, you can set up your own ingress controller, e.g. using [Traefik](https://traefik.io/), [Ambassador](https://www.getambassador.io/) or [Istio](https://istio.io/).  You can find examples for [using Garden with Ambassador](https://github.com/garden-io/garden/tree/v0.9.12/examples/ambassador) and [with Istio](https://github.com/garden-io/garden/tree/v0.9.12/examples/istio) in our [examples directory](https://github.com/garden-io/garden/tree/master/examples).
 
 You'll also need to point one or more DNS entries to your cluster, and configure a TLS certificate for the hostnames
 you will expose for ingress.