Launching the Platform/Self-hosted: On-prem/Prerequisites

Ingress controller

Setup and configure the ingress controller for your self-hosted platform

Overview

Purpose

  • Managing external access to services
  • Load balancing
  • SSL/TLS termination
  • Routing rules

Requirements

  • Kubernetes cluster access
  • Load balancer support
  • Helm (optional)

Deployment options

Install with Helm

helm upgrade --install ingress-nginx ingress-nginx \
  --repo https://kubernetes.github.io/ingress-nginx \
  --namespace ingress-nginx \
  --create-namespace

Wait for the load balancer IP to be assigned:

kubectl get service -n ingress-nginx ingress-nginx-controller \
  --output jsonpath='{.status.loadBalancer.ingress[0].ip}'

Validation

Check pods are running

kubectl get pods -n ingress-nginx

Verify service and ip allocation

kubectl get svc -n ingress-nginx

Information collection

Required values for platform installation

  • Ingress class name (default: nginx)
  • Load balancer IP address
  • Ingress controller namespace
ingress:
  enabled: true
  className: nginx
  # Other ingress settings will be configured in Domain & TLS section

Troubleshooting

No Load Balancer IP

  • Verify cloud provider load balancer service is running
  • Check cloud provider quotas
  • Ensure correct service annotations

Controller Not Ready

  • Check pod logs: kubectl logs -n ingress-nginx <pod-name>
  • Verify resource requirements are met
  • Check network policies

Next steps

Verify ingress controller is running ### Note down the load balancer IP

Proceed to [Domain and TLS

Setup](/documentation/launching-the-platform/self-hosted/prerequisites/domain-and-tls)

Need help? Contact [email protected] if you encounter any issues.