mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-26 21:18:04 +00:00
Add default backend section to ingress controllers
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:
@@ -52,6 +52,17 @@ ingress:
|
|||||||
enable-ssl-passthrough: ""
|
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
|
## 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.
|
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.
|
||||||
|
|||||||
Reference in New Issue
Block a user