Install cert-manager and a working DNS-01 issuer, then migrate from ingress-nginx to NGINX Gateway Fabric and akash-gateway the same way as the with-cert-manager guide.
This path is for clusters that do not yet have cert-manager issuing certificates for the provider. You will complete TLS setup in prep STEP 9 (Helm install, ClusterIssuer, DNS credentials, and Certificates into akash-gateway for wildcard-ingress-tls and akash-default-tls where the prep doc specifies). When cert-manager is issuing in that namespace, continue with the with-cert-manager guide from STEP 1: Install Gateway API CRDs.
Time: 1–2 hours the first time (cert-manager, DNS, and Let’s Encrypt), then the same 30–45 minutes as the with-cert-manager guide.
What you’ll do first (TLS stack)
In Provider installation (prep) – STEP 9, you’ll install and configure:
- cert-manager - ACME client and
Certificateresources - ClusterIssuer - Let’s Encrypt with DNS-01 (Cloudflare, Google, or another supported DNS)
- Secrets in
akash-gateway- At leastwildcard-ingress-tlsandakash-default-tlsas required forakash-gateway
Stop when your Certificate objects show Ready and the Gateway stack can be installed.
Then: Gateway migration
Open Gateway API migration (with cert-manager) and run it from the top. Skip re-explaining your issuer in re-bind TLS if STEP 9 already created the right Secrets; otherwise adjust the Certificate manifests there to match your issuer.
Requirements
Same as the overview: provider v0.11.2 before upgrading to v0.12.0, Helm 3, ingress-nginx on 8443/8444, host ports 80, 443, 8443, 8444, 5002, and a DNS zone you control.