Skip to content

Commit c637ed9

Browse files
committed
Make it clear that it's A or B - helm or YAML
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
1 parent 7ebb6ad commit c637ed9

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/deployment/kubernetes.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,15 +25,15 @@ We have a special guide for minikube here:
2525
--user="$(gcloud config get-value core/account)"
2626
```
2727

28-
### Pick helm or YAML files for deployment
28+
### Pick helm or YAML files for deployment (A or B)
2929

3030
It is recommended to use `helm` to install OpenFaaS so that you can configure your installation to suit your needs. This configuration is considered to be production-ready.
3131

3232
If you have issues using `helm` in a locked-down environment then you can still use the `helm template` command to generate a custom set of YAML to apply using `kubectl`.
3333

3434
Plain YAML files are also provided for x86_64 and armhf, but since they cannot be customized easily it is recommended that you only use these for local development.
3535

36-
#### Deploy with Helm
36+
#### A. Deploy with Helm (for production)
3737

3838
A Helm chart is provided in the `faas-netes` repository. Follow the link below then come back to this guide.
3939

@@ -43,7 +43,7 @@ To enable SSL while using Helm, try one of the following references:
4343

4444
- [Using nginx-ingress and cert-manager](/reference/ssl/kubernetes-with-cert-manager.md)
4545

46-
#### Deploy OpenFaaS
46+
#### B. Deploy using kubectl/YAML (for development-only)
4747

4848
This step assumes you are running `kubectl` on a master host.
4949

0 commit comments

Comments
 (0)