Skip to content

Commit cef4d67

Browse files
committed
Update introduction on k3sup
Given the following Twitter commentary, this commit adds additional context on k3sup and the options available to users for installing OpenFaaS. https://twitter.com/trondhindenes/status/1204112758725328896 Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
1 parent 3018c3c commit cef4d67

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

lab1b.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -210,7 +210,13 @@ The instructions for deploying OpenFaaS change from time to time as we strive to
210210

211211
### Install OpenFaaS
212212

213-
There is a new tool called `k3sup` which can install helm charts, including OpenFaaS. This makes the installation procedure much faster.
213+
There are three ways to install OpenFaaS and you can pick whatever makes sense for you and your team. In this workshop we will use the official installer `k3sup`.
214+
215+
* `k3sup app install` - k3sup installs OpenFaaS using its official helm chart. It can also offer other software with a user-friendly CLI such as `cert-manager` and `nginx-ingress`. It's the easiest and quickest way to get up and running.
216+
217+
* Helm chart - sane defaults and easy to configure through YAML or CLI flags. Secure options such as `helm template` or `helm 3` also exist for those working within restrictive environments
218+
219+
* Plain YAML files - hard-coded settings/values. Tools like Kustomize can offer custom settings
214220

215221
#### Install with `k3sup`
216222

0 commit comments

Comments
 (0)