public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-14 17:13:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add default backend section to ingress controllers

Browse Source 
Add default backend section to ingress controllers. This section
provides a guide and brief explanation on the default backend service.
This commit is contained in:
Nick Gerace
2020-12-07 18:23:19 -05:00
parent 6e7e7e6060
commit 975af8e99f
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rke/latest/en/config-options/add-ons/ingress-controllers/_index.md
+11
View File
@@ -52,6 +52,17 @@ ingress:
enable-ssl-passthrough: ""
```
### Disabling NGINX Ingress Default Backend
As of v0.20.0, you can disable the [default backend service](https://kubernetes.github.io/ingress-nginx/user-guide/default-backend/) for the ingress controller. This is possible because `ingress-nginx` will fall back to a local 404 page, and does not require a backend service. The service can be enabled/disabled with a boolean value.
```yaml
ingress:
default_backend: false
```
> **What happens if the field is omitted?** The value of `default_backend` will default to `true`. This maintains behavior with older versions of `rke`. However, a future version of `rke` will change the default value to `false`.
## Configuring an NGINX Default Certificate
When configuring an ingress object with TLS termination, you must provide it with a certificate used for encryption/decryption. Instead of explicitly defining a certificate each time you configure an ingress, you can set up a custom certificate that's used by default.