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
**What**
- Add note that install using Helm without the Tiller component is
possible and link the user to more detailed instructions
- Move the note about SSL to the advanced section because it seems to
fit there better
Addresses openfaas/faas-netes#302
Signed-off-by: Lucas Roesler <[email protected]>
Copy file name to clipboardExpand all lines: docs/deployment/kubernetes.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,8 +29,6 @@ A guide is available for configuring minikube here:
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
-
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
-
34
32
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
33
36
34
#### A. Deploy with Helm (for production)
@@ -39,9 +37,8 @@ A Helm chart is provided in the `faas-netes` repository. Follow the link below t
To enable SSL while using Helm, try one of the following references:
43
40
44
-
-[Using nginx-ingress and cert-manager](/reference/ssl/kubernetes-with-cert-manager.md)
41
+
**Tiller-less install:** 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`. See the [Chart readme](https://github.com/openfaas/faas-netes/blob/master/chart/openfaas/README.md#deployment-with-helm-template) for detailed instructions.
45
42
46
43
#### B. Deploy using kubectl/YAML (for development-only)
47
44
@@ -204,12 +201,17 @@ If you are running into any issues please check out the troubleshooting guide an
204
201
205
202
This section covers additional advanced topics beyond the initial deployment.
206
203
204
+
#### Deploy with SSL
205
+
To enable SSL while using Helm, try one of the following references:
206
+
207
+
- [Using nginx-ingress and cert-manager](/reference/ssl/kubernetes-with-cert-manager.md)
208
+
207
209
#### Use a private registry with Kubernetes
208
210
209
211
If you are using a hosted private Docker registry ([Docker Hub](https://hub.docker.com/), or other),
210
212
in order to check how to configure it, please visit the Kubernetes [documentation](https://kubernetes.io/docs/concepts/containers/images/#using-a-private-registry).
211
213
212
-
If you try to deploy using `faas-cli deploy` it will fail because the Kubernetes kubelet component will not have credentials to authorize the pull request.
214
+
If you try to deploy using `faas-cli deploy` it will fail because the Kubernetes kubelet component will not have credentials to authorize the pull request.
213
215
214
216
Once you have pushed an image to a private registry using `faas-cli push` follow the instructions below to either create a pull secret that can be referenced by each function which needs it, or create a secret for the ServiceAccount in the `openfaas-fn` namespace so that any functions which need it can make use of it.
0 commit comments