You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/deployment/kubernetes.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,15 +25,15 @@ We have a special guide for minikube here:
25
25
--user="$(gcloud config get-value core/account)"
26
26
```
27
27
28
-
### Pick helm or YAML files for deployment
28
+
### Pick helm or YAML files for deployment (A or B)
29
29
30
30
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.
31
31
32
32
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`.
33
33
34
34
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.
35
35
36
-
#### Deploy with Helm
36
+
#### A. Deploy with Helm (for production)
37
37
38
38
A Helm chart is provided in the `faas-netes` repository. Follow the link below then come back to this guide.
39
39
@@ -43,7 +43,7 @@ To enable SSL while using Helm, try one of the following references:
43
43
44
44
-[Using nginx-ingress and cert-manager](/reference/ssl/kubernetes-with-cert-manager.md)
45
45
46
-
#### Deploy OpenFaaS
46
+
#### B. Deploy using kubectl/YAML (for development-only)
47
47
48
48
This step assumes you are running `kubectl` on a master host.
0 commit comments