Available in editions: CE, BE, SE, SE+, EE
The module lifecycle stage: General Availability
Pay attention to the global parameter publicDomainTemplate, if you are turning the module on. If the parameter is not specified, the Ingress resources for DKP service components (dashboard, user-auth, grafana, upmeter, etc.) will not be created.
Ingress controllers are configured using the IngressNginxController Custom Resource.
The module has 13 alerts.
The module is enabled by default in the following bundles: Default, Managed.
The module is disabled by default in the Minimal bundle.
Settings
The module is configured using the ModuleConfig custom resource named ingress-nginx (learn more about setting up Deckhouse…).
Example of the ModuleConfig/ingress-nginx resource for configuring the module:
apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
name: ingress-nginx
spec:
version: 1
enabled: true
settings: # <-- Module parameters from the "Parameters" section below.
Parameters
Schema version: 1
- objectsettings
- settings.defaultControllerVersion
The version of the ingress-nginx controller that is used for all controllers by default if the
controllerVersionparameter is omitted in the IngressNginxController CR.Default:
1.10 - booleansettings.highAvailability
Manually enable the high availability mode.
By default, Deckhouse automatically decides whether to enable the HA mode. Click here to learn more about the HA mode for modules.
Example:
highAvailability: true