Update limit for function name limit

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>

Author: alexellis

docs/deployment/troubleshooting.md

@@ -94,9 +94,17 @@ Common issues:
 * You haven't created a secret which is required for your function to start. Check your function request or stack.yml, and create any missing secrets.
 * Your function is crashing due to an error in your code, check the logs.
 
-### I think my function's name is too long
+### Is my function's name too long?
 
-When using Kubernetes, a function's name should be no longer than 45 characters if it also mounts a secret. This is due to how the projected volume for the Pod's secrets is named.
+When using Kubernetes along with the Function CRD, a function's name can be no longer than 63 characters. This is due to a limitation on the length of label selectors within Kubernetes.
+
+If you need longer names for the sake of organisation, then consider [using namespaces](/reference/namespaces) to partition your functions.
+
+For example:
+
+`project-skunkworks-long-function-name` could be shortened to `long-function-name`, and then placed in the `project-skunkworks` namespace, effectively going longer than the 63 character limit for organisation.
+
+OpenFaaS namespaces are available in faasd and OpenFaaS for Enterprises.
 
 ### My function is timing out
 

docs/openfaas-pro/billing-metrics.md

@@ -21,9 +21,6 @@ To start receiving events with detailed usage metrics you need to enable meterin
 You will need to create an `endpointSecret` which will be shared with the HTTP receiver, and used to sign the webhook payload.
 
 ```bash
-# If openssl is not available on your system, use the following:
-head -c 32 /dev/urandom | base64 | cut -d "-" -f1 > billing-endpoint-secret.txt
-
 # openssl is preferred to generate a random secret:
 openssl rand -base64 32 > billing-endpoint-secret.txt
 

docs/openfaas-pro/iam/auditing.md

@@ -23,9 +23,6 @@ To start receiving auditing events you need to enable auditing and configure a w
 You will need to create an `endpointSecret` which will be shared with the HTTP receiver, and used to sign the webhook payload.
 
 ```bash
-# If openssl is not available on your system, use the following:
-head -c 32 /dev/urandom | base64 | cut -d "-" -f1 > ./event-webhook-secret.txt
-
 # openssl is preferred to generate a random secret:
 openssl rand -base64 32 > ./event-webhook-secret.txt
 

docs/reference/namespaces.md

@@ -97,15 +97,15 @@ Deploy the stack.yml and invoke the function:
 ```sh
 faas-cli deploy
 
-head -c 16 /dev/urandom | faas-cli invoke --namespace dev stronghash
+openssl rand -base64 32 | faas-cli invoke --namespace dev stronghash
 ```
 
 Override the namespace configured in the stack.yml when deploying the function and test:
 
 ```sh
 faas-cli deploy --namespace staging-fn
 
-head -c 16 /dev/urandom | faas-cli invoke --namespace staging-fn stronghash
+openssl rand -base64 32 | faas-cli invoke --namespace staging-fn stronghash
 ```
 
 ## Controlling network access