Update to mention LoadBalancer and chart folder
@@ -23,12 +23,21 @@ You can create a separate namespace for OpenFaaS core services and functions (re
```
$ kubectl create ns openfaas
$ kubectl create ns openfaas-fn
+```
+
+This command should be run from within the `faas-netes/chart` folder or equivalent:
+```
$ helm upgrade --install openfaas openfaas/ \
--namespace openfaas \
--set functionNamespace=openfaas-fn
```
+By default NodePorts will be created for the API Gateway and Prometheus.
+
+> Note: If you're running on a cloud such as AKS or GKE you will need to pass an additional flag of `--set serviceType=LoadBalancer` to tell `helm` to create LoadBalancer objects instead. An alternative to using multiple LoadBalancers is to install an Ingress controller.
+
+
Or to use the default namespace (not recommended):
```
@@ -37,8 +46,6 @@ $ helm upgrade --install openfaas openfaas/ \
--set functionNamespace=default
```
-By default you will have NodePorts available for each service such as the API gateway and Prometheus
-
### Deploy with an IngressController
In order to make use of automatic ingress settings you will need an IngressController in your cluster such as Traefik or Nginx.
