Skip to content

Commit 29dedc9

Browse files
LucasRoesleralexellis
authored andcommitted
add tillerless install note in k8s install
**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]>
1 parent 9aa63e4 commit 29dedc9

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

docs/deployment/kubernetes.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,6 @@ A guide is available for configuring minikube here:
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

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-
3432
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.
3533

3634
#### 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
3937

4038
* [OpenFaaS Helm chart](https://github.com/openfaas/faas-netes/blob/master/HELM.md)
4139

42-
To enable SSL while using Helm, try one of the following references:
4340

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.
4542

4643
#### B. Deploy using kubectl/YAML (for development-only)
4744

@@ -204,12 +201,17 @@ If you are running into any issues please check out the troubleshooting guide an
204201
205202
This section covers additional advanced topics beyond the initial deployment.
206203
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+
207209
#### Use a private registry with Kubernetes
208210
209211
If you are using a hosted private Docker registry ([Docker Hub](https://hub.docker.com/), or other),
210212
in order to check how to configure it, please visit the Kubernetes [documentation](https://kubernetes.io/docs/concepts/containers/images/#using-a-private-registry).
211213
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.
213215
214216
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.
215217

0 commit comments

Comments
 (0)