Quick Setup: Gateway Controller
Warning
Only follow this section if no existing Gateway Controller was found.
Choose one of the following options based on your environment:
Option A: NGINX Gateway Fabric
-
Install Gateway API CRDs:
-
Deploy the NGINX Gateway Fabric Controller:
-
Verify all pods are running:
-
Confirm the gateway class is available:
You should see
nginxin the output. Usenginxas yourgatewayClassName.
Option B: Cloud-Native Gateway Controllers
Choose the appropriate controller for your cloud platform:
- AWS: AWS Load Balancer Controller
- GCP: GKE Gateway Controller
- Azure: Azure Application Gateway for Containers
Refer to your cloud provider's documentation for installation steps.
(Optional) TLS Configuration Using cert-manager
Tip
Skip this section if you don't need HTTPS/TLS for QMigrator. You can add TLS later.
Install cert-manager
-
Add the cert-manager Helm repository:
-
Install cert-manager with Gateway API support:
-
Verify cert-manager pods are running:
Create a Certificate Issuer
Choose between ClusterIssuer (cluster-wide) or Issuer (namespace-specific):
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
name: letsencrypt
spec:
acme:
server: https://acme-v02.api.letsencrypt.org/directory
privateKeySecretRef:
name: letsencrypt
solvers:
- http01:
gatewayHTTPRoute:
parentRefs:
- name: qmig-gateway
Apply the configuration:
Update the namespace ({{ Namespace }}):
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
name: letsencrypt
namespace: {{ Namespace }}
spec:
acme:
server: https://acme-v02.api.letsencrypt.org/directory
privateKeySecretRef:
name: letsencrypt
solvers:
- http01:
gatewayHTTPRoute:
parentRefs:
- name: qmig-gateway
Apply the configuration: