Gateway API migration

Replace ingress-nginx with NGINX Gateway Fabric and the akash-gateway chart on an existing cluster.

This migration moves provider TCP from ingress-nginx to the Kubernetes Gateway API. HTTPS ends at akash-gateway (listeners https-wildcard and https-custom); you need NGF on port 443. New builds should use the prep and install guides instead.

Time: Depends on path; budget about 30–60 minutes of hands-on work plus certificate wait time.

Choose your path

  • With cert-manager - cert-manager and a ClusterIssuer are already installed; you still add new Certificate objects and TLS Secrets in akash-gateway (the chart does not use certs left in ingress-nginx or other namespaces by default). Same issuer, new namespace and secret names the chart expects.
  • Without cert-manager - You install cert-manager, a DNS-01 issuer, and TLS secrets using prep STEP 9, then follow the same Gateway steps.

Requirements (both)

Provider v0.11.2 before upgrading to v0.12.0, Helm 3, ingress-nginx on 8443/8444, host ports 80, 443, 8443, 8444, and 5002 free, and a public DNS zone. DNS-01 options are in STEP 9 (TLS) and the cert-manager DNS-01 docs.

Edit page on github
Updates & Maintenance With cert-manager