Remove instructions for plain YAML and store

alexellis · alexellis · commit 605e7d5a24a6 · 2020-10-09T18:38:58.000+01:00
The plain YAML will remain in the repo, but complicates
instructions for beginners.

The store and initial function instructions are covered
elsewhere in the docs and in the workshop.

Signed-off-by: Alex Ellis (OpenFaaS Ltd) &lt;alexellis2@gmail.com&gt;
diff --git a/docs/deployment/kubernetes.md b/docs/deployment/kubernetes.md
@@ -19,7 +19,7 @@ Before deploying OpenFaaS, you should provision a Kubernetes cluster. There are
 Once you have a cluster, you can follow the detailed instructions on this page.
 
 * Install OpenFaaS CLI
-* Deploy OpenFaaS from static YAML, via helm, or via new YAML files generated with `helm template`
+* Deploy OpenFaaS using via helm or arkade
 * Find your OpenFaaS gateway address
 * Log in, deploy a function, and try out the UI.
 
@@ -85,19 +85,17 @@ The CLI is also available on `brew` for MacOS users, however it may lag behind b
 brew install faas-cli
 ```
 
-### Pick `arkade`, `helm` or plain YAML files
+### Install the OpenFaaS chart using `arkade` or `helm`
 
 There are three recommended ways to install OpenFaaS and you can pick whatever makes sense for you and your team.
 
-* `arkade install` - arkade installs OpenFaaS to Kubernetes using its official helm chart and is the easiest and quickest way to get up and running.
-
-* 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.
-
-* Plain YAML files - not recommended for anything beyond testing since the options are generated and hard-coded. Tools like Kustomize can offer the ability to custom the files.
+1) Helm with `arkade install` - arkade installs OpenFaaS to Kubernetes using its official helm chart and is the easiest and quickest way to get up and running.
+2) `helm` client - 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.
+3) With GitOps tooling. You can install OpenFaaS and keep it up to date with [Flux](https://github.com/fluxcd/flux) or [ArgoCD](https://argoproj.github.io/argo-cd/).
 
 Guidelines are also provided for [preparing for production](/architecture/production/) and for [performance testing](/architecture/performance).
 
-#### A. Deploy with `arkade` (fastest option)
+#### 1) Deploy the Chart with `arkade` (fastest option)
 
 The `arkade install` command installs OpenFaaS using its official helm chart, but without using `tiller`, a [component which is insecure by default](https://engineering.bitnami.com/articles/running-helm-in-production.html). arkade can also install other important software for OpenFaaS users such as `cert-manager` and `nginx-ingress`. It's the easiest and quickest way to get up and running.
 
@@ -135,7 +133,7 @@ Other options for installation are available with `arkade install openfaas --hel
 
 For cloud users run `kubectl get -n openfaas svc/gateway-external` and look for `EXTERNAL-IP`. This is your gateway address.
 
-#### B. Deploy with Helm (for production, most configurable)
+#### 2) Deploy the Chart with `helm`
 
 A Helm chart is provided in the `faas-netes` repository. Follow the link below then come back to this page.
 
@@ -146,63 +144,6 @@ A Helm chart is provided in the `faas-netes` repository. Follow the link below t
         
         See the [Chart readme](https://github.com/openfaas/faas-netes/blob/master/chart/openfaas/README.md#deployment-with-helm-template) for how to generate your own static YAML files using `helm template`.
 
-#### C. Deploy using `kubectl` and plain YAML (for development-only)
-
-You can run these commands on your computer if you have `kubectl` and `KUBECONFIG` file available.
-
-* Clone the repository
-
-    ```bash
-    $ git clone https://github.com/openfaas/faas-netes
-    ```
-
-* Deploy the whole stack
-
-    This command is split into two parts so that the OpenFaaS namespaces are always created first:
-
-    * `openfaas` - for OpenFaaS services
-    * `openfaas-fn` - for functions
-
-    ```bash
-    $ kubectl apply -f https://raw.githubusercontent.com/openfaas/faas-netes/master/namespaces.yml
-    ```
-
-    Create a password for the gateway:
-
-    ```bash
-    # generate a random password
-    PASSWORD=$(head -c 12 /dev/urandom | shasum| cut -d' ' -f1)
-
-    kubectl -n openfaas create secret generic basic-auth \
-    --from-literal=basic-auth-user=admin \
-    --from-literal=basic-auth-password="$PASSWORD"
-    ```
-
-    Now deploy OpenFaaS:
-
-    ```bash
-    $ cd faas-netes && \
-    kubectl apply -f ./yaml
-    ```
-
-    Set your `OPENFAAS_URL`, if using a NodePort this may be `127.0.0.1:31112`.
-
-    If you're using a remote cluster, or you're not sure then you can also port-forward the gateway to your machine for this step.
-
-    ```bash
-    kubectl port-forward svc/gateway -n openfaas 31112:8080 &
-    ```
-
-    Now log in:
-    ```bash
-    export OPENFAAS_URL=http://127.0.0.1:31112
-
-    echo -n $PASSWORD | faas-cli login --password-stdin
-    ```
-
-    !!! note
-        For deploying on a cloud that supports Kubernetes *LoadBalancers* you may also want to apply the configuration in: `cloud/lb.yml`.
-
 #### Notes for Raspberry Pi & 32-bit ARM (armhf)
 
 Use `arkade` to install OpenFaaS, it will determine the correct files to use to install OpenFaaS.
@@ -258,69 +199,6 @@ You can also find a list of [community tutorials, events, and videos](https://gi
 
 A walk-through video shows auto-scaling in action and the Prometheus UI: [walk-through video](https://www.youtube.com/watch?v=0DbrLsUvaso).
 
-### Deploy a function
-
-Functions can be deployed using the REST API, UI, CLI, or Function Store. Continue below to deploy your first sample function.
-
-#### Deploy functions from the OpenFaaS Function Store
-
-You can find many different sample functions from the community through the OpenFaaS Function Store. The Function Store is built into the UI portal and also available via the CLI.
-
-You may need to pass the `--gateway` / `-g` flag to each `faas-cli` command or alternatively you can set an environmental variable such as:
-
-```bash
-export OPENFAAS_URL=http://127.0.0.1:31112
-```
-
-To search the store:
-
-```bash
-$ faas-cli store list
-```
-
-To deploy `figlet`:
-
-```bash
-$ faas-cli store deploy figlet
-```
-
-Now find the function deployed in the cluster and invoke it.
-
-```bash
-$ faas-cli list
-$ echo "OpenFaaS!" | faas-cli invoke figlet
-```
-
-You can also access the Function Store from the Portal UI and find a range of functions covering everything from machine-learning to network tools.
-
-##### Build your first Python function
-
-[Your first serverless Python function with OpenFaaS](https://blog.alexellis.io/first-faas-python-function/)
-
-#### Use the UI
-
-Access your gateway using the URL from the steps above.
-
-Click "New Function" and fill it out with the following:
-
-| Field      | Value                        |
--------------|------------------------------|
-| Service    | nodeinfo                     |
-| Image      | functions/nodeinfo:latest    |
-| fProcess   | node main.js                 |
-| Network    | default                      |
-
-* Test the function
-
-Your function will appear after a few seconds and you can click "Invoke"
-
-The function can also be invoked through the CLI:
-
-```bash
-$ echo -n "" | faas-cli invoke --gateway http://kubernetes-ip:31112 nodeinfo
-$ echo -n "verbose" | faas-cli invoke --gateway http://kubernetes-ip:31112 nodeinfo
-```
-
 ### Troubleshooting
 
 If you are running into any issues please check out the troubleshooting guide and search the documentation / past issues before raising an issue.
