Routing Secrets are kubernetes Secrets of type
kubernetes.io/tls and marked by the
presence of the label
epinio.io/routing. Note that the value of that label is not
relevant, just its presence.
Usage is automatic. When deploying an application into a namespace containing routing secrets, and requesting a route for a domain covered by the secrets (exactly, or as wildcard), then the application chart is passed the name of the secret to use for the Ingress of that route.
The matching process prefers exact matches over wildcard matches, and a shorter wildcard over a longer one.
Troubleshooting Question Sheet
- Is the Secret of type
- Is the Secret labeled with
- Is the Secret in the application's namespace ?
- Does the application route match the domain covered by the Secret ?
- If the application chart is a custom chart, does it support routing secrets ?