Skip to main content

Configure and customize Ingress and NGINX Controller using Overrides

This guide explains how to configure Ingress resources and the NGINX controller in your Harness deployment, including how to customize its behavior using overrides.

For more information, go to Ingress Controllers in the Kubernetes documentation.

Ingress Configuration​

Enable Ingress​

global:
  ingress:
    enabled: true
    className: "harness"  # Specifies the Ingress controller class

Host Configuration​

global:
  ingress:
    hosts:
      - 'myhost.example.com'  # Replace with your domain

TLS Configuration​

global:
  ingress:
    tls:
      - secretName: my-tls-secret
        hosts:
          - myhost.example.com

Advanced Configuration Options​

Path Type​

global:
  ingress:
    pathType: ImplementationSpecific  # Other options: Prefix, Exact

Custom Annotations​

global:
  ingress:
    objects:
      annotations:
        nginx.ingress.kubernetes.io/proxy-body-size: "50m"
        nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"

Host Configuration​

global:
  ingress:
    disableHostInIngress: false  # Set to true to disable host rules in Ingress

Example Full Configuration​

global:
  ingress:
    enabled: true
    className: "harness"
    objects:
      annotations:
        nginx.ingress.kubernetes.io/proxy-body-size: "50m"
        nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"
    disableHostInIngress: false
    pathType: ImplementationSpecific
    hosts:
      - 'myhost.example.com'
    tls:
      - secretName: my-tls-secret
        hosts:
          - myhost.example.com

Configure ingress controller arguments​

You can configure nginx-ingress-controller arguments using the following overrides.

nginx:
  controller:
    watchNamespace: ""
    updateStatus: true
    httpPort: 8080
    httpsPort: 8443
    watchIngressWithoutClass: true
    defaultSSLCertificate: ""
    configMap: ""
    defaultBackendService: ""
    publishService: ""
    electionId: ""
    controllerClass: ""

Add extra arguments​

Use the following to add extra arguments.

nginx:
  controller:
    extraCommandArgs:
      - --argument=example-argument

Create cluster roles​

The following creates a clusterRole and clusterRoleBindings.

nginx:
  clusterRole:
    create: true

Troubleshooting​

Common issues and solutions:

  1. 502 Bad Gateway

    • Check upstream service availability
    • Verify proxy timeout settings
    • Check service name and port configuration

  2. 404 Not Found

    • Verify ingress path configuration
    • Check rewrite-target annotation if used
    • Confirm service endpoint existence
    • Check nginx controller logs for errors

  3. SSL/TLS Issues

    • Verify TLS secret exists
    • Check certificate validity

  4. Performance Issues

    • Increase nginx controller replicas if needed
    • Check nginx controller logs for errors