You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`controller.hostNetwork` | Enables the Ingress Controller pods to use the host's network namespace. | false
156
156
`controller.nginxDebug` | Enables debugging for NGINX. Uses the `nginx-debug` binary. Requires `error-log-level: debug` in the ConfigMap via `controller.config.entries`. | false
157
157
`controller.logLevel` | The log level of the Ingress Controller. | 1
158
+
`controller.image.digest ` | The image digest of the Ingress Controller. | None
158
159
`controller.image.repository` | The image repository of the Ingress Controller. | nginx/nginx-ingress
159
-
`controller.image.tag` | The tag of the Ingress Controller image. | 2.3.0
160
+
`controller.image.tag` | The tag of the Ingress Controller image. | 2.4.0
160
161
`controller.image.pullPolicy` | The pull policy for the Ingress Controller image. | IfNotPresent
162
+
`controller.lifecycle` | The lifecycle of the Ingress Controller pods. | {}
163
+
`controller.customConfigMap` | The name of the custom ConfigMap used by the Ingress Controller. If set, then the default config is ignored. | ""
161
164
`controller.config.name` | The name of the ConfigMap used by the Ingress Controller. | Autogenerated
162
165
`controller.config.annotations` | The annotations of the Ingress Controller configmap. | {}
163
166
`controller.config.entries` | The entries of the ConfigMap for customizing NGINX configuration. See [ConfigMap resource docs](https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/) for the list of supported ConfigMap keys. | {}
164
167
`controller.customPorts` | A list of custom ports to expose on the NGINX ingress controller pod. Follows the conventional Kubernetes yaml syntax for container ports. | []
165
-
`controller.defaultTLS.cert` | The base64-encoded TLS certificate for the default HTTPS server. If not specified, a pre-generated self-signed certificate is used. **Note:**It is recommended that you specify your own certificate. | A pre-generated self-signed certificate.
166
-
`controller.defaultTLS.key` | The base64-encoded TLS key for the default HTTPS server. **Note:**If not specified, a pre-generated key is used. It is recommended that you specify your own key. | A pre-generated key.
167
-
`controller.defaultTLS.secret` | The secret with a TLS certificate and key for the default HTTPS server. The value must follow the following format: `<namespace>/<name>`. Used as an alternative to specifying a certificate and key using `controller.defaultTLS.cert` and `controller.defaultTLS.key` parameters. | None
168
+
`controller.defaultTLS.cert` | The base64-encoded TLS certificate for the default HTTPS server. **Note:** By default, a pre-generated self-signed certificate is used. It is recommended that you specify your own certificate. Alternatively, omitting the default server secret completely will configure NGINX to reject TLS connections to the default server. | A pre-generated self-signed certificate.
169
+
`controller.defaultTLS.key` | The base64-encoded TLS key for the default HTTPS server. **Note:**By default, a pre-generated key is used. It is recommended that you specify your own key. Alternatively, omitting the default server secret completely will configure NGINX to reject TLS connections to the default server. | A pre-generated key.
170
+
`controller.defaultTLS.secret` | The secret with a TLS certificate and key for the default HTTPS server. The value must follow the following format: `<namespace>/<name>`. Used as an alternative to specifying a certificate and key using `controller.defaultTLS.cert` and `controller.defaultTLS.key` parameters. **Note:** Alternatively, omitting the default server secret completely will configure NGINX to reject TLS connections to the default server. | None
168
171
`controller.wildcardTLS.cert` | The base64-encoded TLS certificate for every Ingress/VirtualServer host that has TLS enabled but no secret specified. If the parameter is not set, for such Ingress/VirtualServer hosts NGINX will break any attempt to establish a TLS connection. | None
169
172
`controller.wildcardTLS.key` | The base64-encoded TLS key for every Ingress/VirtualServer host that has TLS enabled but no secret specified. If the parameter is not set, for such Ingress/VirtualServer hosts NGINX will break any attempt to establish a TLS connection. | None
170
173
`controller.wildcardTLS.secret` | The secret with a TLS certificate and key for every Ingress/VirtualServer host that has TLS enabled but no secret specified. The value must follow the following format: `<namespace>/<name>`. Used as an alternative to specifying a certificate and key using `controller.wildcardTLS.cert` and `controller.wildcardTLS.key` parameters. | None
`controller.replicaCount` | The number of replicas of the Ingress Controller deployment. | 1
182
185
`controller.ingressClass` | A class of the Ingress Controller. An IngressClass resource with the name equal to the class must be deployed. Otherwise, the Ingress Controller will fail to start. The Ingress Controller only processes resources that belong to its class - i.e. have the "ingressClassName" field resource equal to the class. The Ingress Controller processes all the VirtualServer/VirtualServerRoute/TransportServer resources that do not have the "ingressClassName" field for all versions of kubernetes. | nginx
183
186
`controller.setAsDefaultIngress` | New Ingresses without an `"ingressClassName"` field specified will be assigned the class specified in `controller.ingressClass`. | false
184
-
`controller.watchNamespace` | Namespace to watch for Ingress resources. By default the Ingress Controller watches all namespaces. | ""
187
+
`controller.watchNamespace` | Comma separated list of namespaces the Ingress Controller should watch for resources. By default the Ingress Controller watches all namespaces. | ""
185
188
`controller.enableCustomResources` | Enable the custom resources. | true
186
189
`controller.enablePreviewPolicies` | Enable preview policies. This parameter is deprecated. To enable OIDC Policies please use `controller.enableOIDC` instead. | false
`controller.service.httpsPort.targetPort` | The target port of the HTTPS port of the Ingress Controller service. | 443
218
221
`controller.serviceAccount.name` | The name of the service account of the Ingress Controller pods. Used for RBAC. | Autogenerated
219
222
`controller.serviceAccount.imagePullSecretName` | The name of the secret containing docker registry credentials. Secret must exist in the same namespace as the helm release. | ""
223
+
`controller.serviceMonitor.name` | The name of the serviceMonitor. | Autogenerated
224
+
`controller.serviceMonitor.create` | Create a ServiceMonitor custom resource. | false
225
+
`controller.serviceMonitor.labels` | Kubernetes object labels to attach to the serviceMonitor object. | ""
226
+
`controller.serviceMonitor.selectorMatchLabels` | A set of labels to allow the selection of endpoints for the ServiceMonitor. | ""
227
+
`controller.serviceMonitor.endpoints` | A list of endpoints allowed as part of this ServiceMonitor. | ""
220
228
`controller.reportIngressStatus.enable` | Updates the address field in the status of Ingress resources with an external address of the Ingress Controller. You must also specify the source of the external address either through an external service via `controller.reportIngressStatus.externalService`, `controller.reportIngressStatus.ingressLink` or the `external-status-address` entry in the ConfigMap via `controller.config.entries`. **Note:**`controller.config.entries.external-status-address` takes precedence over the others. | true
221
229
`controller.reportIngressStatus.externalService` | Specifies the name of the service with the type LoadBalancer through which the Ingress Controller is exposed externally. The external address of the service is used when reporting the status of Ingress, VirtualServer and VirtualServerRoute resources. `controller.reportIngressStatus.enable` must be set to `true`. The default is autogenerated and enabled when `controller.service.create` is set to `true` and `controller.service.type` is set to `LoadBalancer`. | Autogenerated
222
230
`controller.reportIngressStatus.ingressLink` | Specifies the name of the IngressLink resource, which exposes the Ingress Controller pods via a BIG-IP system. The IP of the BIG-IP system is used when reporting the status of Ingress, VirtualServer and VirtualServerRoute resources. `controller.reportIngressStatus.enable` must be set to `true`. | ""
`controller.reportIngressStatus.annotations` | The annotations of the leader election configmap. | {}
226
234
`controller.pod.annotations` | The annotations of the Ingress Controller pod. | {}
227
235
`controller.pod.extraLabels` | The additional extra labels of the Ingress Controller pod. | {}
228
-
`controller.appprotect.enable` | Enables the App Protect module in the Ingress Controller. | false
236
+
`controller.appprotect.enable` | Enables the App Protect WAF module in the Ingress Controller. | false
229
237
`controller.appprotectdos.enable` | Enables the App Protect DoS module in the Ingress Controller. | false
230
238
`controller.appprotectdos.debug` | Enable debugging for App Protect DoS. | false
231
239
`controller.appprotectdos.maxDaemons` | Max number of ADMD instances. | 1
232
240
`controller.appprotectdos.maxWorkers` | Max number of nginx processes to support. | Number of CPU cores in the machine
233
241
`controller.appprotectdos.memory` | RAM memory size to consume in MB. | 50% of free RAM in the container or 80MB, the smaller
234
242
`controller.readyStatus.enable` | Enables the readiness endpoint `"/nginx-ready"`. The endpoint returns a success code when NGINX has loaded all the config after the startup. This also configures a readiness probe for the Ingress Controller pods that uses the readiness endpoint. | true
235
243
`controller.readyStatus.port` | The HTTP port for the readiness endpoint. | 8081
244
+
`controller.readyStatus.initialDelaySeconds` | The number of seconds after the Ingress Controller pod has started before readiness probes are initiated. | 0
236
245
`controller.enableLatencyMetrics` | Enable collection of latency metrics for upstreams. Requires `prometheus.create`. | false
237
246
`controller.minReadySeconds` | Specifies the minimum number of seconds for which a newly created Pod should be ready without any of its containers crashing, for it to be considered available. [docs](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#min-ready-seconds) | 0
238
247
`controller.strategy` | Specifies the strategy used to replace old Pods by new ones. [docs](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy) | {}
248
+
`controller.disableIPV6` | Disable IPV6 listeners explicitly for nodes that do not support the IPV6 stack. | false
239
249
`rbac.create` | Configures RBAC. | true
240
250
`prometheus.create` | Expose NGINX or NGINX Plus metrics in the Prometheus format. | false
241
251
`prometheus.port` | Configures the port to scrape the metrics. | 9113
0 commit comments