Split out TLS into its own sections

Breaks out a page for TLS for the gateway and one for functions
and makes a breaking change to move away from the "ssl" URL
which was introduced years ago.

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

Author: alexellis

docs/architecture/invocations.md

@@ -70,7 +70,7 @@ The connection between the caller and the function remains connected until the i
 
 See the below for TLS termination, custom domains and mapping various functions to traditional REST paths:
 
-* [TLS with OpenFaaS](/reference/ssl/kubernetes-with-cert-manager)
+* [TLS with OpenFaaS](/reference/tls-openfaas)
 
 ## How do asynchronous invocations work?
 
@@ -98,7 +98,7 @@ See also: [Learn how to manage your functions with kubectl](https://www.openfaas
 
 OpenFaaS For Enterprise offers authentication using JWT tokens obtained through an Open ID Connect (OIDC) flow and an Identity Provider (IdP).
 
-* [TLS with OpenFaaS](/reference/ssl/kubernetes-with-cert-manager)
+* [TLS with OpenFaaS](/reference/tls-openfaas)
 * [Identity and Access Management (IAM)](/openfaas-pro/iam/overview/)
 
 For functions, you should provide your own authentication mechanism, such as a shared token, OIDC, HMAC or basic authentication.

docs/deployment/kubernetes.md

@@ -16,7 +16,7 @@ The OpenFaaS helm chart ships with its own stack that includes NATS, Prometheus
 
 The chart can be installed with helm and kubectl or arkade, we recommend arkade which also prints out everything you need to know to access the UI and deploy your first function.
 
-From there, you should consider: adding a [TLS certificate](/reference/ssl/kubernetes-with-cert-manager) and trying out one of our training courses commissioned by the CNCF/LinuxFoundation, or an eBook.
+From there, you should consider: adding a [TLS certificate](/reference/tls-openfaas) and trying out one of our training courses commissioned by the CNCF/LinuxFoundation, or an eBook.
 
 See also: [Training materials and eBooks](/tutorials/training)
 
@@ -204,7 +204,7 @@ Also, ensure any [default load-balancer timeouts within GKE](https://cloud.googl
 To enable TLS while using Helm, try one of the following references:
 
 * [Get TLS for OpenFaaS the easy way with arkade](https://blog.alexellis.io/tls-the-easy-way-with-openfaas-and-k3sup/)
-* [Configure TLS with nginx-ingress and cert-manager](/reference/ssl/kubernetes-with-cert-manager/)
+* [Configure TLS with nginx-ingress and cert-manager](/reference/tls-openfaas)
 
 ### Setting an Image Pull Policy for your functions
 

docs/deployment/pro.md

@@ -118,9 +118,8 @@ If this is your first time installing the dashboard, we recommend using "localho
 Then add the Helm chart repo, update it and deploy the chart, running `helm repo update` before each upgrade, to make sure you have the latest versions.
 
 ```sh
-helm repo update
-
-helm upgrade --install openfaas \
+helm repo update && \
+  helm upgrade --install openfaas \
   --install openfaas/openfaas \
   --namespace openfaas \
   -f ./values-custom.yaml

docs/reference/rest-api.md

@@ -130,7 +130,7 @@ Note that in some clusters, the default DNS lookup of "svc.cluster.local" may be
 
 You can expose Functions with a REST-like mapping or on custom subdomains with the `FunctionIngress` Custom Resource:
 
-* See also: [Custom domains and REST-like mappings for functions](https://blog.exit.o6s.io/reference/ssl/kubernetes-with-cert-manager/)
+* See also: [Custom domains and REST-like mappings for functions](/reference/tls-functions)
 
 ### Deploy a function