Update yaml file list to yaml folder
@@ -46,24 +46,23 @@ This step assumes you are running `kubectl` on a master host.
$ git clone https://github.com/openfaas/faas-netes
```
-Deploy a synchronous or asynchronous stack. If you're using OpenFaaS for the first time we recommend the synchronous stack. The asynchronous stack also includes NATS Streaming for queuing.
+Deploy a stack with asynchronous functionality provided by NATS Streaming.
-* Deploy the synchronous stack
+* Deploy the whole stack
-```
-$ cd faas-netes
-$ kubectl apply -f ./faas.yml,monitoring.yml,rbac.yml
-```
-
-Or
+This command is split into two parts so that the OpenFaaS namespaces are always created first:
-* Deploy the asynchronous stack
+* openfaas - for OpenFaaS services
+* openfaas-fn - for functions
```
-$ cd faas-netes
-$ kubectl apply -f ./faas.async.yml,nats.yml,monitoring.yml,rbac.yml
+$ cd faas-netes && \
+ kubectl apply -f ./yaml/namespaces.yml && \
+ kubectl apply -f ./yaml
```
+Note: RBAC is optional but encouraged and enabled by default.
+
Asynchronous invocation works by queuing requests with NATS Streaming. An alternative implementation is available with Kafka in an [open PR](https://github.com/openfaas/faas/pull/311).
* See also: [Asynchronous function guide](https://github.com/openfaas/faas/blob/master/guide/asynchronous.md)
@@ -96,10 +95,12 @@ There are currently no sample functions built into this stack, but we can deploy
* Install the CLI
```
-$ curl -sL cli.openfaas.com | sudo sh
+$ curl -sL https://cli.openfaas.com | sudo sh
```
-Then clone some samples to deploy on your cluster.
+If you like you can also run the script via a non-root user. Then the faas-cli binary is downloaded to the current working directory instead.
+
+* Then clone some samples to deploy on your cluster.
```
$ git clone https://github.com/openfaas/faas-cli
