[jb3]

This pull request migrates ingress traffic management from the deprecated NGINX Ingress Controller to NGINX Gateway Fabric. It introduces new Kubernetes resources and configuration for the nginx-gateway namespace, updates DNS records to point to the new gateway, and ensures that certificates are properly reflected into the new namespace. The most important changes are summarized below.

Migration to NGINX Gateway Fabric:

• Added a new nginx-gateway namespace with supporting manifests for NGINX Gateway Fabric, including a README with installation instructions (namespace.yaml, README.md, values.yaml). [1] [2] [3]
• Introduced certificate management resources for the gateway, including a self-signed CA, issuer, and certificates for mutual TLS between the control and data planes (certificates.yaml, client-certs.yaml). [1] [2]
• Defined a new Gateway resource with HTTP and HTTPS listeners for pythondiscord.com and pydis.wtf domains (gateway.yaml).

DNS and Routing Updates:

• Removed the old envoy-lb.box A record and replaced all references to it with a new nginx-gf.box A record in DNS zone files. Updated all relevant CNAMEs to point to nginx-gf.box.pydis.wtf. (box.yaml, code-jam.yaml). [1] [2] [3]

Certificate Reflection Configuration:

• Updated certificate resources to allow and auto-reflect secrets into the new nginx-gateway namespace, ensuring TLS certificates are available for the gateway (owlcorp.uk.yaml, pydis.wtf.yaml, pythondiscord.com.yaml). [1] [2] [3]

[github-actions]

Thanks!