tree: dec3fcfc225b767906cc0c1d837262ad0e3cbfc5 [path history] [tgz]
  1. changelog/
  2. ci/
  3. templates/
  4. tests/
  5. .helmignore
  6. Chart.yaml
  7. OWNERS
  8. README.md
  9. README.md.gotmpl
  10. requirements.lock
  11. values.yaml
charts/ingress-nginx/README.md

ingress-nginx

ingress-nginx Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer

Version: 4.10.1 AppVersion: 1.10.1

To use, add ingressClassName: nginx spec field or the kubernetes.io/ingress.class: nginx annotation to your Ingress resources.

This chart bootstraps an ingress-nginx deployment on a Kubernetes cluster using the Helm package manager.

Requirements

Kubernetes: >=1.21.0-0

Get Repo Info

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update

Install Chart

Important: only helm3 is supported

helm install [RELEASE_NAME] ingress-nginx/ingress-nginx

The command deploys ingress-nginx on the Kubernetes cluster in the default configuration.

See configuration below.

See helm install for command documentation.

Uninstall Chart

helm uninstall [RELEASE_NAME]

This removes all the Kubernetes components associated with the chart and deletes the release.

See helm uninstall for command documentation.

Upgrading Chart

helm upgrade [RELEASE_NAME] [CHART] --install

See helm upgrade for command documentation.

Migrating from stable/nginx-ingress

There are two main ways to migrate a release from stable/nginx-ingress to ingress-nginx/ingress-nginx chart:

  1. For Nginx Ingress controllers used for non-critical services, the easiest method is to uninstall the old release and install the new one
  2. For critical services in production that require zero-downtime, you will want to:
    1. Install a second Ingress controller
    2. Redirect your DNS traffic from the old controller to the new controller
    3. Log traffic from both controllers during this changeover
    4. Uninstall the old controller once traffic has fully drained from it

Note that there are some different and upgraded configurations between the two charts, described by Rimas Mocevicius from JFrog in the "Upgrading to ingress-nginx Helm chart" section of Migrating from Helm chart nginx-ingress to ingress-nginx. As the ingress-nginx/ingress-nginx chart continues to update, you will want to check current differences by running helm configuration commands on both charts.

Configuration

See Customizing the Chart Before Installing. To see all configurable options with detailed comments, visit the chart's values.yaml, or run these configuration commands:

helm show values ingress-nginx/ingress-nginx

PodDisruptionBudget

Note that the PodDisruptionBudget resource will only be defined if the replicaCount is greater than one, else it would make it impossible to evacuate a node. See gh issue #7127 for more info.

Prometheus Metrics

The Ingress-Nginx Controller can export Prometheus metrics, by setting controller.metrics.enabled to true.

You can add Prometheus annotations to the metrics service using controller.metrics.service.annotations. Alternatively, if you use the Prometheus Operator, you can enable ServiceMonitor creation using controller.metrics.serviceMonitor.enabled. And set controller.metrics.serviceMonitor.additionalLabels.release="prometheus". "release=prometheus" should match the label configured in the prometheus servicemonitor ( see kubectl get servicemonitor prometheus-kube-prom-prometheus -oyaml -n prometheus)

ingress-nginx nginx_status page/stats server

Previous versions of this chart had a controller.stats.* configuration block, which is now obsolete due to the following changes in Ingress-Nginx Controller:

  • In 0.16.1, the vts (virtual host traffic status) dashboard was removed
  • In 0.23.0, the status page at port 18080 is now a unix socket webserver only available at localhost. You can use curl --unix-socket /tmp/nginx-status-server.sock http://localhost/nginx_status inside the controller container to access it locally, or use the snippet from nginx-ingress changelog to re-enable the http server

ExternalDNS Service Configuration

Add an ExternalDNS annotation to the LoadBalancer service:

controller:
  service:
    annotations:
      external-dns.alpha.kubernetes.io/hostname: kubernetes-example.com.

AWS L7 ELB with SSL Termination

Annotate the controller as shown in the nginx-ingress l7 patch:

controller:
  service:
    targetPorts:
      http: http
      https: http
    annotations:
      service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:XX-XXXX-X:XXXXXXXXX:certificate/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX
      service.beta.kubernetes.io/aws-load-balancer-backend-protocol: "http"
      service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "https"
      service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: '3600'

Additional Internal Load Balancer

This setup is useful when you need both external and internal load balancers but don't want to have multiple ingress controllers and multiple ingress objects per application.

By default, the ingress object will point to the external load balancer address, but if correctly configured, you can make use of the internal one if the URL you are looking up resolves to the internal load balancer's URL.

You'll need to set both the following values:

controller.service.internal.enabled controller.service.internal.annotations

If one of them is missing the internal load balancer will not be deployed. Example you may have controller.service.internal.enabled=true but no annotations set, in this case no action will be taken.

controller.service.internal.annotations varies with the cloud service you're using.

Example for AWS:

controller:
  service:
    internal:
      enabled: true
      annotations:
        # Create internal NLB
        service.beta.kubernetes.io/aws-load-balancer-scheme: "internal"
        # Create internal ELB(Deprecated)
        # service.beta.kubernetes.io/aws-load-balancer-internal: "true"
        # Any other annotation can be declared here.

Example for GCE:

controller:
  service:
    internal:
      enabled: true
      annotations:
        # Create internal LB. More information: https://cloud.google.com/kubernetes-engine/docs/how-to/internal-load-balancing
        # For GKE versions 1.17 and later
        networking.gke.io/load-balancer-type: "Internal"
        # For earlier versions
        # cloud.google.com/load-balancer-type: "Internal"

        # Any other annotation can be declared here.

Example for Azure:

controller:
  service:
      annotations:
        # Create internal LB
        service.beta.kubernetes.io/azure-load-balancer-internal: "true"
        # Any other annotation can be declared here.

Example for Oracle Cloud Infrastructure:

controller:
  service:
      annotations:
        # Create internal LB
        service.beta.kubernetes.io/oci-load-balancer-internal: "true"
        # Any other annotation can be declared here.

The load balancer annotations of more cloud service providers can be found: Internal load balancer.

An use case for this scenario is having a split-view DNS setup where the public zone CNAME records point to the external balancer URL while the private zone CNAME records point to the internal balancer URL. This way, you only need one ingress kubernetes object.

Optionally you can set controller.service.loadBalancerIP if you need a static IP for the resulting LoadBalancer.

Ingress Admission Webhooks

With nginx-ingress-controller version 0.25+, the Ingress-Nginx Controller pod exposes an endpoint that will integrate with the validatingwebhookconfiguration Kubernetes feature to prevent bad ingress from being added to the cluster. This feature is enabled by default since 0.31.0.

With nginx-ingress-controller in 0.25.* work only with kubernetes 1.14+, 0.26 fix this issue

How the Chart Configures the Hooks

A validating and configuration requires the endpoint to which the request is sent to use TLS. It is possible to set up custom certificates to do this, but in most cases, a self-signed certificate is enough. The setup of this component requires some more complex orchestration when using helm. The steps are created to be idempotent and to allow turning the feature on and off without running into helm quirks.

  1. A pre-install hook provisions a certificate into the same namespace using a format compatible with provisioning using end user certificates. If the certificate already exists, the hook exits.
  2. The Ingress-Nginx Controller pod is configured to use a TLS proxy container, which will load that certificate.
  3. Validating and Mutating webhook configurations are created in the cluster.
  4. A post-install hook reads the CA from the secret created by step 1 and patches the Validating and Mutating webhook configurations. This process will allow a custom CA provisioned by some other process to also be patched into the webhook configurations. The chosen failure policy is also patched into the webhook configurations

Alternatives

It should be possible to use cert-manager/cert-manager if a more complete solution is required.

You can enable automatic self-signed TLS certificate provisioning via cert-manager by setting the controller.admissionWebhooks.certManager.enabled value to true.

Please ensure that cert-manager is correctly installed and configured.

Helm Error When Upgrading: spec.clusterIP: Invalid value: ""

If you are upgrading this chart from a version between 0.31.0 and 1.2.2 then you may get an error like this:

Error: UPGRADE FAILED: Service "?????-controller" is invalid: spec.clusterIP: Invalid value: "": field is immutable

Detail of how and why are in this issue but to resolve this you can set xxxx.service.omitClusterIP to true where xxxx is the service referenced in the error.

As of version 1.26.0 of this chart, by simply not providing any clusterIP value, invalid: spec.clusterIP: Invalid value: "": field is immutable will no longer occur since clusterIP: "" will not be rendered.

Values

KeyTypeDefaultDescription
commonLabelsobject{}
controller.addHeadersobject{}Will add custom headers before sending response traffic to the client according to: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#add-headers
controller.admissionWebhooks.annotationsobject{}
controller.admissionWebhooks.certManager.admissionCert.durationstring""
controller.admissionWebhooks.certManager.enabledboolfalse
controller.admissionWebhooks.certManager.rootCert.durationstring""
controller.admissionWebhooks.certificatestring"/usr/local/certificates/cert"
controller.admissionWebhooks.createSecretJob.namestring"create"
controller.admissionWebhooks.createSecretJob.resourcesobject{}
controller.admissionWebhooks.createSecretJob.securityContextobject{"allowPrivilegeEscalation":false,"capabilities":{"drop":["ALL"]},"readOnlyRootFilesystem":true,"runAsNonRoot":true,"runAsUser":65532,"seccompProfile":{"type":"RuntimeDefault"}}Security context for secret creation containers
controller.admissionWebhooks.enabledbooltrue
controller.admissionWebhooks.existingPspstring""Use an existing PSP instead of creating one
controller.admissionWebhooks.extraEnvslist[]Additional environment variables to set
controller.admissionWebhooks.failurePolicystring"Fail"Admission Webhook failure policy to use
controller.admissionWebhooks.keystring"/usr/local/certificates/key"
controller.admissionWebhooks.labelsobject{}Labels to be added to admission webhooks
controller.admissionWebhooks.namestring"admission"
controller.admissionWebhooks.namespaceSelectorobject{}
controller.admissionWebhooks.objectSelectorobject{}
controller.admissionWebhooks.patch.enabledbooltrue
controller.admissionWebhooks.patch.image.digeststring"sha256:36d05b4077fb8e3d13663702fa337f124675ba8667cbd949c03a8e8ea6fa4366"
controller.admissionWebhooks.patch.image.imagestring"ingress-nginx/kube-webhook-certgen"
controller.admissionWebhooks.patch.image.pullPolicystring"IfNotPresent"
controller.admissionWebhooks.patch.image.registrystring"registry.k8s.io"
controller.admissionWebhooks.patch.image.tagstring"v1.4.1"
controller.admissionWebhooks.patch.labelsobject{}Labels to be added to patch job resources
controller.admissionWebhooks.patch.networkPolicy.enabledboolfalseEnable 'networkPolicy' or not
controller.admissionWebhooks.patch.nodeSelector."kubernetes.io/os"string"linux"
controller.admissionWebhooks.patch.podAnnotationsobject{}
controller.admissionWebhooks.patch.priorityClassNamestring""Provide a priority class name to the webhook patching job #
controller.admissionWebhooks.patch.securityContextobject{}Security context for secret creation & webhook patch pods
controller.admissionWebhooks.patch.tolerationslist[]
controller.admissionWebhooks.patchWebhookJob.namestring"patch"
controller.admissionWebhooks.patchWebhookJob.resourcesobject{}
controller.admissionWebhooks.patchWebhookJob.securityContextobject{"allowPrivilegeEscalation":false,"capabilities":{"drop":["ALL"]},"readOnlyRootFilesystem":true,"runAsNonRoot":true,"runAsUser":65532,"seccompProfile":{"type":"RuntimeDefault"}}Security context for webhook patch containers
controller.admissionWebhooks.portint8443
controller.admissionWebhooks.service.annotationsobject{}
controller.admissionWebhooks.service.externalIPslist[]
controller.admissionWebhooks.service.loadBalancerSourceRangeslist[]
controller.admissionWebhooks.service.servicePortint443
controller.admissionWebhooks.service.typestring"ClusterIP"
controller.affinityobject{}Affinity and anti-affinity rules for server scheduling to nodes # Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity #
controller.allowSnippetAnnotationsboolfalseThis configuration defines if Ingress Controller should allow users to set their own *-snippet annotations, otherwise this is forbidden / dropped when users add those annotations. Global snippets in ConfigMap are still respected
controller.annotationsobject{}Annotations to be added to the controller Deployment or DaemonSet #
controller.autoscaling.annotationsobject{}
controller.autoscaling.behaviorobject{}
controller.autoscaling.enabledboolfalse
controller.autoscaling.maxReplicasint11
controller.autoscaling.minReplicasint1
controller.autoscaling.targetCPUUtilizationPercentageint50
controller.autoscaling.targetMemoryUtilizationPercentageint50
controller.autoscalingTemplatelist[]
controller.configobject{}Will add custom configuration options to Nginx https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/
controller.configAnnotationsobject{}Annotations to be added to the controller config configuration configmap.
controller.configMapNamespacestring""Allows customization of the configmap / nginx-configmap namespace; defaults to $(POD_NAMESPACE)
controller.containerNamestring"controller"Configures the controller container name
controller.containerPortobject{"http":80,"https":443}Configures the ports that the nginx-controller listens on
controller.containerSecurityContextobject{}Security context for controller containers
controller.customTemplate.configMapKeystring""
controller.customTemplate.configMapNamestring""
controller.dnsConfigobject{}Optionally customize the pod dnsConfig.
controller.dnsPolicystring"ClusterFirst"Optionally change this to ClusterFirstWithHostNet in case you have 'hostNetwork: true'. By default, while using host network, name resolution uses the host's DNS. If you wish nginx-controller to keep resolving names inside the k8s network, use ClusterFirstWithHostNet.
controller.electionIDstring""Election ID to use for status update, by default it uses the controller name combined with a suffix of 'leader'
controller.enableAnnotationValidationsboolfalse
controller.enableMimallocbooltrueEnable mimalloc as a drop-in replacement for malloc. # ref: https://github.com/microsoft/mimalloc #
controller.enableTopologyAwareRoutingboolfalseThis configuration enables Topology Aware Routing feature, used together with service annotation service.kubernetes.io/topology-mode="auto" Defaults to false
controller.existingPspstring""Use an existing PSP instead of creating one
controller.extraArgsobject{}Additional command line arguments to pass to Ingress-Nginx Controller E.g. to specify the default SSL certificate you can use
controller.extraContainerslist[]Additional containers to be added to the controller pod. See https://github.com/lemonldap-ng-controller/lemonldap-ng-controller as example.
controller.extraEnvslist[]Additional environment variables to set
controller.extraInitContainerslist[]Containers, which are run before the app containers are started.
controller.extraModuleslist[]Modules, which are mounted into the core nginx image. See values.yaml for a sample to add opentelemetry module
controller.extraVolumeMountslist[]Additional volumeMounts to the controller main container.
controller.extraVolumeslist[]Additional volumes to the controller pod.
controller.healthCheckHoststring""Address to bind the health check endpoint. It is better to set this option to the internal node address if the Ingress-Nginx Controller is running in the hostNetwork: true mode.
controller.healthCheckPathstring"/healthz"Path of the health check endpoint. All requests received on the port defined by the healthz-port parameter are forwarded internally to this path.
controller.hostAliaseslist[]Optionally customize the pod hostAliases.
controller.hostNetworkboolfalseRequired for use with CNI based kubernetes installations (such as ones set up by kubeadm), since CNI and hostport don't mix yet. Can be deprecated once https://github.com/kubernetes/kubernetes/issues/23920 is merged
controller.hostPort.enabledboolfalseEnable 'hostPort' or not
controller.hostPort.ports.httpint80'hostPort' http port
controller.hostPort.ports.httpsint443'hostPort' https port
controller.hostnameobject{}Optionally customize the pod hostname.
controller.image.allowPrivilegeEscalationboolfalse
controller.image.chrootboolfalse
controller.image.digeststring"sha256:e24f39d3eed6bcc239a56f20098878845f62baa34b9f2be2fd2c38ce9fb0f29e"
controller.image.digestChrootstring"sha256:c155954116b397163c88afcb3252462771bd7867017e8a17623e83601bab7ac7"
controller.image.imagestring"ingress-nginx/controller"
controller.image.pullPolicystring"IfNotPresent"
controller.image.readOnlyRootFilesystemboolfalse
controller.image.registrystring"registry.k8s.io"
controller.image.runAsNonRootbooltrue
controller.image.runAsUserint101
controller.image.seccompProfile.typestring"RuntimeDefault"
controller.image.tagstring"v1.10.1"
controller.ingressClassstring"nginx"For backwards compatibility with ingress.class annotation, use ingressClass. Algorithm is as follows, first ingressClassName is considered, if not present, controller looks for ingress.class annotation
controller.ingressClassByNameboolfalseProcess IngressClass per name (additionally as per spec.controller).
controller.ingressClassResourceobject{"controllerValue":"k8s.io/ingress-nginx","default":false,"enabled":true,"name":"nginx","parameters":{}}This section refers to the creation of the IngressClass resource. IngressClasses are immutable and cannot be changed after creation. We do not support namespaced IngressClasses, yet, so a ClusterRole and a ClusterRoleBinding is required.
controller.ingressClassResource.controllerValuestring"k8s.io/ingress-nginx"Controller of the IngressClass. An Ingress Controller looks for IngressClasses it should reconcile by this value. This value is also being set as the --controller-class argument of this Ingress Controller. Ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class
controller.ingressClassResource.defaultboolfalseIf true, Ingresses without ingressClassName get assigned to this IngressClass on creation. Ingress creation gets rejected if there are multiple default IngressClasses. Ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#default-ingress-class
controller.ingressClassResource.enabledbooltrueCreate the IngressClass or not
controller.ingressClassResource.namestring"nginx"Name of the IngressClass
controller.ingressClassResource.parametersobject{}A link to a custom resource containing additional configuration for the controller. This is optional if the controller consuming this IngressClass does not require additional parameters. Ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class
controller.keda.apiVersionstring"keda.sh/v1alpha1"
controller.keda.behaviorobject{}
controller.keda.cooldownPeriodint300
controller.keda.enabledboolfalse
controller.keda.maxReplicasint11
controller.keda.minReplicasint1
controller.keda.pollingIntervalint30
controller.keda.restoreToOriginalReplicaCountboolfalse
controller.keda.scaledObject.annotationsobject{}
controller.keda.triggerslist[]
controller.kindstring"Deployment"Use a DaemonSet or Deployment
controller.labelsobject{}Labels to be added to the controller Deployment or DaemonSet and other resources that do not have option to specify labels #
controller.lifecycleobject{"preStop":{"exec":{"command":["/wait-shutdown"]}}}Improve connection draining when ingress controller pod is deleted using a lifecycle hook: With this new hook, we increased the default terminationGracePeriodSeconds from 30 seconds to 300, allowing the draining of connections up to five minutes. If the active connections end before that, the pod will terminate gracefully at that time. To effectively take advantage of this feature, the Configmap feature worker-shutdown-timeout new value is 240s instead of 10s. #
controller.livenessProbe.failureThresholdint5
controller.livenessProbe.httpGet.pathstring"/healthz"
controller.livenessProbe.httpGet.portint10254
controller.livenessProbe.httpGet.schemestring"HTTP"
controller.livenessProbe.initialDelaySecondsint10
controller.livenessProbe.periodSecondsint10
controller.livenessProbe.successThresholdint1
controller.livenessProbe.timeoutSecondsint1
controller.maxmindLicenseKeystring""Maxmind license key to download GeoLite2 Databases. # https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases
controller.metrics.enabledboolfalse
controller.metrics.portint10254
controller.metrics.portNamestring"metrics"
controller.metrics.prometheusRule.additionalLabelsobject{}
controller.metrics.prometheusRule.enabledboolfalse
controller.metrics.prometheusRule.ruleslist[]
controller.metrics.service.annotationsobject{}
controller.metrics.service.externalIPslist[]List of IP addresses at which the stats-exporter service is available # Ref: https://kubernetes.io/docs/concepts/services-networking/service/#external-ips #
controller.metrics.service.labelsobject{}Labels to be added to the metrics service resource
controller.metrics.service.loadBalancerSourceRangeslist[]
controller.metrics.service.servicePortint10254
controller.metrics.service.typestring"ClusterIP"
controller.metrics.serviceMonitor.additionalLabelsobject{}
controller.metrics.serviceMonitor.annotationsobject{}
controller.metrics.serviceMonitor.enabledboolfalse
controller.metrics.serviceMonitor.metricRelabelingslist[]
controller.metrics.serviceMonitor.namespacestring""
controller.metrics.serviceMonitor.namespaceSelectorobject{}
controller.metrics.serviceMonitor.relabelingslist[]
controller.metrics.serviceMonitor.scrapeIntervalstring"30s"
controller.metrics.serviceMonitor.targetLabelslist[]
controller.minAvailableint1Minimum available pods set in PodDisruptionBudget. Define either 'minAvailable' or 'maxUnavailable', never both.
controller.minReadySecondsint0minReadySeconds to avoid killing pods before we are ready #
controller.namestring"controller"
controller.networkPolicy.enabledboolfalseEnable 'networkPolicy' or not
controller.nodeSelectorobject{"kubernetes.io/os":"linux"}Node labels for controller pod assignment # Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ #
controller.opentelemetry.containerSecurityContext.allowPrivilegeEscalationboolfalse
controller.opentelemetry.containerSecurityContext.capabilities.drop[0]string"ALL"
controller.opentelemetry.containerSecurityContext.readOnlyRootFilesystembooltrue
controller.opentelemetry.containerSecurityContext.runAsNonRootbooltrue
controller.opentelemetry.containerSecurityContext.runAsUserint65532The image's default user, inherited from its base image cgr.dev/chainguard/static.
controller.opentelemetry.containerSecurityContext.seccompProfile.typestring"RuntimeDefault"
controller.opentelemetry.enabledboolfalse
controller.opentelemetry.image.digeststring"sha256:13bee3f5223883d3ca62fee7309ad02d22ec00ff0d7033e3e9aca7a9f60fd472"
controller.opentelemetry.image.distrolessbooltrue
controller.opentelemetry.image.imagestring"ingress-nginx/opentelemetry"
controller.opentelemetry.image.registrystring"registry.k8s.io"
controller.opentelemetry.image.tagstring"v20230721-3e2062ee5"
controller.opentelemetry.namestring"opentelemetry"
controller.opentelemetry.resourcesobject{}
controller.podAnnotationsobject{}Annotations to be added to controller pods #
controller.podLabelsobject{}Labels to add to the pod container metadata
controller.podSecurityContextobject{}Security context for controller pods
controller.priorityClassNamestring""
controller.proxySetHeadersobject{}Will add custom headers before sending traffic to backends according to https://github.com/kubernetes/ingress-nginx/tree/main/docs/examples/customization/custom-headers
controller.publishServiceobject{"enabled":true,"pathOverride":""}Allows customization of the source of the IP address or FQDN to report in the ingress status field. By default, it reads the information provided by the service. If disable, the status field reports the IP address of the node or nodes where an ingress controller pod is running.
controller.publishService.enabledbooltrueEnable 'publishService' or not
controller.publishService.pathOverridestring""Allows overriding of the publish service to bind to Must be /<service_name>
controller.readinessProbe.failureThresholdint3
controller.readinessProbe.httpGet.pathstring"/healthz"
controller.readinessProbe.httpGet.portint10254
controller.readinessProbe.httpGet.schemestring"HTTP"
controller.readinessProbe.initialDelaySecondsint10
controller.readinessProbe.periodSecondsint10
controller.readinessProbe.successThresholdint1
controller.readinessProbe.timeoutSecondsint1
controller.replicaCountint1
controller.reportNodeInternalIpboolfalseBare-metal considerations via the host network https://kubernetes.github.io/ingress-nginx/deploy/baremetal/#via-the-host-network Ingress status was blank because there is no Service exposing the Ingress-Nginx Controller in a configuration using the host network, the default --publish-service flag used in standard cloud setups does not apply
controller.resources.requests.cpustring"100m"
controller.resources.requests.memorystring"90Mi"
controller.scope.enabledboolfalseEnable 'scope' or not
controller.scope.namespacestring""Namespace to limit the controller to; defaults to $(POD_NAMESPACE)
controller.scope.namespaceSelectorstring""When scope.enabled == false, instead of watching all namespaces, we watching namespaces whose labels only match with namespaceSelector. Format like foo=bar. Defaults to empty, means watching all namespaces.
controller.service.annotationsobject{}Annotations to be added to the external controller service. See controller.service.internal.annotations for annotations to be added to the internal controller service.
controller.service.appProtocolbooltrueDeclare the app protocol of the external HTTP and HTTPS listeners or not. Supersedes provider-specific annotations for declaring the backend protocol. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#application-protocol
controller.service.clusterIPstring""Pre-defined cluster internal IP address of the external controller service. Take care of collisions with existing services. This value is immutable. Set once, it can not be changed without deleting and re-creating the service. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#choosing-your-own-ip-address
controller.service.enableHttpbooltrueEnable the HTTP listener on both controller services or not.
controller.service.enableHttpsbooltrueEnable the HTTPS listener on both controller services or not.
controller.service.enabledbooltrueEnable controller services or not. This does not influence the creation of either the admission webhook or the metrics service.
controller.service.external.enabledbooltrueEnable the external controller service or not. Useful for internal-only deployments.
controller.service.externalIPslist[]List of node IP addresses at which the external controller service is available. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#external-ips
controller.service.externalTrafficPolicystring""External traffic policy of the external controller service. Set to "Local" to preserve source IP on providers supporting it. Ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
controller.service.internal.annotationsobject{}Annotations to be added to the internal controller service. Mandatory for the internal controller service to be created. Varies with the cloud service. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
controller.service.internal.appProtocolbooltrueDeclare the app protocol of the internal HTTP and HTTPS listeners or not. Supersedes provider-specific annotations for declaring the backend protocol. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#application-protocol
controller.service.internal.clusterIPstring""Pre-defined cluster internal IP address of the internal controller service. Take care of collisions with existing services. This value is immutable. Set once, it can not be changed without deleting and re-creating the service. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#choosing-your-own-ip-address
controller.service.internal.enabledboolfalseEnable the internal controller service or not. Remember to configure controller.service.internal.annotations when enabling this.
controller.service.internal.externalIPslist[]List of node IP addresses at which the internal controller service is available. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#external-ips
controller.service.internal.externalTrafficPolicystring""External traffic policy of the internal controller service. Set to "Local" to preserve source IP on providers supporting it. Ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
controller.service.internal.ipFamilieslist["IPv4"]List of IP families (e.g. IPv4, IPv6) assigned to the internal controller service. This field is usually assigned automatically based on cluster configuration and the ipFamilyPolicy field. Ref: https://kubernetes.io/docs/concepts/services-networking/dual-stack/#services
controller.service.internal.ipFamilyPolicystring"SingleStack"Represents the dual-stack capabilities of the internal controller service. Possible values are SingleStack, PreferDualStack or RequireDualStack. Fields ipFamilies and clusterIP depend on the value of this field. Ref: https://kubernetes.io/docs/concepts/services-networking/dual-stack/#services
controller.service.internal.loadBalancerClassstring""Load balancer class of the internal controller service. Used by cloud providers to select a load balancer implementation other than the cloud provider default. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#load-balancer-class
controller.service.internal.loadBalancerIPstring""Deprecated: Pre-defined IP address of the internal controller service. Used by cloud providers to connect the resulting load balancer service to a pre-existing static IP. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer
controller.service.internal.loadBalancerSourceRangeslist[]Restrict access to the internal controller service. Values must be CIDRs. Allows any source address by default.
controller.service.internal.nodePorts.httpstring""Node port allocated for the internal HTTP listener. If left empty, the service controller allocates one from the configured node port range.
controller.service.internal.nodePorts.httpsstring""Node port allocated for the internal HTTPS listener. If left empty, the service controller allocates one from the configured node port range.
controller.service.internal.nodePorts.tcpobject{}Node port mapping for internal TCP listeners. If left empty, the service controller allocates them from the configured node port range. Example: tcp: 8080: 30080
controller.service.internal.nodePorts.udpobject{}Node port mapping for internal UDP listeners. If left empty, the service controller allocates them from the configured node port range. Example: udp: 53: 30053
controller.service.internal.portsobject{}
controller.service.internal.sessionAffinitystring""Session affinity of the internal controller service. Must be either "None" or "ClientIP" if set. Defaults to "None". Ref: https://kubernetes.io/docs/reference/networking/virtual-ips/#session-affinity
controller.service.internal.targetPortsobject{}
controller.service.internal.typestring""Type of the internal controller service. Defaults to the value of controller.service.type. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types
controller.service.ipFamilieslist["IPv4"]List of IP families (e.g. IPv4, IPv6) assigned to the external controller service. This field is usually assigned automatically based on cluster configuration and the ipFamilyPolicy field. Ref: https://kubernetes.io/docs/concepts/services-networking/dual-stack/#services
controller.service.ipFamilyPolicystring"SingleStack"Represents the dual-stack capabilities of the external controller service. Possible values are SingleStack, PreferDualStack or RequireDualStack. Fields ipFamilies and clusterIP depend on the value of this field. Ref: https://kubernetes.io/docs/concepts/services-networking/dual-stack/#services
controller.service.labelsobject{}Labels to be added to both controller services.
controller.service.loadBalancerClassstring""Load balancer class of the external controller service. Used by cloud providers to select a load balancer implementation other than the cloud provider default. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#load-balancer-class
controller.service.loadBalancerIPstring""Deprecated: Pre-defined IP address of the external controller service. Used by cloud providers to connect the resulting load balancer service to a pre-existing static IP. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer
controller.service.loadBalancerSourceRangeslist[]Restrict access to the external controller service. Values must be CIDRs. Allows any source address by default.
controller.service.nodePorts.httpstring""Node port allocated for the external HTTP listener. If left empty, the service controller allocates one from the configured node port range.
controller.service.nodePorts.httpsstring""Node port allocated for the external HTTPS listener. If left empty, the service controller allocates one from the configured node port range.
controller.service.nodePorts.tcpobject{}Node port mapping for external TCP listeners. If left empty, the service controller allocates them from the configured node port range. Example: tcp: 8080: 30080
controller.service.nodePorts.udpobject{}Node port mapping for external UDP listeners. If left empty, the service controller allocates them from the configured node port range. Example: udp: 53: 30053
controller.service.ports.httpint80Port the external HTTP listener is published with.
controller.service.ports.httpsint443Port the external HTTPS listener is published with.
controller.service.sessionAffinitystring""Session affinity of the external controller service. Must be either "None" or "ClientIP" if set. Defaults to "None". Ref: https://kubernetes.io/docs/reference/networking/virtual-ips/#session-affinity
controller.service.targetPorts.httpstring"http"Port of the ingress controller the external HTTP listener is mapped to.
controller.service.targetPorts.httpsstring"https"Port of the ingress controller the external HTTPS listener is mapped to.
controller.service.typestring"LoadBalancer"Type of the external controller service. Ref: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types
controller.shareProcessNamespaceboolfalse
controller.sysctlsobject{}sysctls for controller pods # Ref: https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/
controller.tcp.annotationsobject{}Annotations to be added to the tcp config configmap
controller.tcp.configMapNamespacestring""Allows customization of the tcp-services-configmap; defaults to $(POD_NAMESPACE)
controller.terminationGracePeriodSecondsint300terminationGracePeriodSeconds to avoid killing pods before we are ready # wait up to five minutes for the drain of connections #
controller.tolerationslist[]Node tolerations for server scheduling to nodes with taints # Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/ #
controller.topologySpreadConstraintslist[]Topology spread constraints rely on node labels to identify the topology domain(s) that each Node is in. # Ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/ #
controller.udp.annotationsobject{}Annotations to be added to the udp config configmap
controller.udp.configMapNamespacestring""Allows customization of the udp-services-configmap; defaults to $(POD_NAMESPACE)
controller.updateStrategyobject{}The update strategy to apply to the Deployment or DaemonSet #
controller.watchIngressWithoutClassboolfalseProcess Ingress objects without ingressClass annotation/ingressClassName field Overrides value for --watch-ingress-without-class flag of the controller binary Defaults to false
defaultBackend.affinityobject{}
defaultBackend.autoscaling.annotationsobject{}
defaultBackend.autoscaling.enabledboolfalse
defaultBackend.autoscaling.maxReplicasint2
defaultBackend.autoscaling.minReplicasint1
defaultBackend.autoscaling.targetCPUUtilizationPercentageint50
defaultBackend.autoscaling.targetMemoryUtilizationPercentageint50
defaultBackend.containerSecurityContextobject{}Security context for default backend containers
defaultBackend.enabledboolfalse
defaultBackend.existingPspstring""Use an existing PSP instead of creating one
defaultBackend.extraArgsobject{}
defaultBackend.extraConfigMapslist[]
defaultBackend.extraEnvslist[]Additional environment variables to set for defaultBackend pods
defaultBackend.extraVolumeMountslist[]
defaultBackend.extraVolumeslist[]
defaultBackend.image.allowPrivilegeEscalationboolfalse
defaultBackend.image.imagestring"defaultbackend-amd64"
defaultBackend.image.pullPolicystring"IfNotPresent"
defaultBackend.image.readOnlyRootFilesystembooltrue
defaultBackend.image.registrystring"registry.k8s.io"
defaultBackend.image.runAsNonRootbooltrue
defaultBackend.image.runAsUserint65534
defaultBackend.image.seccompProfile.typestring"RuntimeDefault"
defaultBackend.image.tagstring"1.5"
defaultBackend.labelsobject{}Labels to be added to the default backend resources
defaultBackend.livenessProbe.failureThresholdint3
defaultBackend.livenessProbe.initialDelaySecondsint30
defaultBackend.livenessProbe.periodSecondsint10
defaultBackend.livenessProbe.successThresholdint1
defaultBackend.livenessProbe.timeoutSecondsint5
defaultBackend.minAvailableint1
defaultBackend.minReadySecondsint0minReadySeconds to avoid killing pods before we are ready #
defaultBackend.namestring"defaultbackend"
defaultBackend.networkPolicy.enabledboolfalseEnable 'networkPolicy' or not
defaultBackend.nodeSelectorobject{"kubernetes.io/os":"linux"}Node labels for default backend pod assignment # Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ #
defaultBackend.podAnnotationsobject{}Annotations to be added to default backend pods #
defaultBackend.podLabelsobject{}Labels to add to the pod container metadata
defaultBackend.podSecurityContextobject{}Security context for default backend pods
defaultBackend.portint8080
defaultBackend.priorityClassNamestring""
defaultBackend.readinessProbe.failureThresholdint6
defaultBackend.readinessProbe.initialDelaySecondsint0
defaultBackend.readinessProbe.periodSecondsint5
defaultBackend.readinessProbe.successThresholdint1
defaultBackend.readinessProbe.timeoutSecondsint5
defaultBackend.replicaCountint1
defaultBackend.resourcesobject{}
defaultBackend.service.annotationsobject{}
defaultBackend.service.externalIPslist[]List of IP addresses at which the default backend service is available # Ref: https://kubernetes.io/docs/concepts/services-networking/service/#external-ips #
defaultBackend.service.loadBalancerSourceRangeslist[]
defaultBackend.service.servicePortint80
defaultBackend.service.typestring"ClusterIP"
defaultBackend.serviceAccount.automountServiceAccountTokenbooltrue
defaultBackend.serviceAccount.createbooltrue
defaultBackend.serviceAccount.namestring""
defaultBackend.tolerationslist[]Node tolerations for server scheduling to nodes with taints # Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/ #
defaultBackend.updateStrategyobject{}The update strategy to apply to the Deployment or DaemonSet #
dhParamstring""A base64-encoded Diffie-Hellman parameter. This can be generated with: `openssl dhparam 4096 2> /dev/null
imagePullSecretslist[]Optional array of imagePullSecrets containing private registry credentials # Ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
namespaceOverridestring""Override the deployment namespace; defaults to .Release.Namespace
podSecurityPolicy.enabledboolfalse
portNamePrefixstring""Prefix for TCP and UDP ports names in ingress controller service # Some cloud providers, like Yandex Cloud may have a requirements for a port name regex to support cloud load balancer integration
rbac.createbooltrue
rbac.scopeboolfalse
revisionHistoryLimitint10Rollback limit #
serviceAccount.annotationsobject{}Annotations for the controller service account
serviceAccount.automountServiceAccountTokenbooltrue
serviceAccount.createbooltrue
serviceAccount.namestring""
tcpobject{}TCP service key-value pairs # Ref: https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/exposing-tcp-udp-services.md #
udpobject{}UDP service key-value pairs # Ref: https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/exposing-tcp-udp-services.md #