How to configure the Envoy Gateway and HTTPRoute to properly redirect with 302 from the secondary domain to the main domain with TLS?

[devent]

Hi. I have multiple domains for one web site, and the main domain should be www.site.com and other domains should just redirect to the main site with 302. What is the best/correct way to do that with the new Kubernetes Gateway API? All domains should also request a certificate via cert-manager from LetsEncrypt with Http0 method.

Right now I have just one Gateway for each domain and one HTTPRoute for each domain that use the gateways.

node-1:~$ kubectl -n wordpress get Gateway
NAME        CLASS             ADDRESS         PROGRAMMED   AGE
gateway-0   internet-public   192.168.250.4   True         17d ---> www.site.com, tls: Terminate, cert-manager created cert
gateway-1   internet-public   192.168.250.5   True         17d ---> site.com, tls: Terminate, cert-manager created cert
gateway-2   internet-public   192.168.250.6   True         17d ---> www.other.com, tls: Terminate, cert-manager created cert
gateway-3   internet-public   192.168.250.7   True         17d ---> other.com, tls: Terminate, cert-manager created cert
node-1:~$ kubectl -n wordpress get httproute
NAME        HOSTNAMES                   AGE
gateway-0   ["www.site.com]    17d  ---> main domain, backendRef wordpress
gateway-1   ["site.com"]        17d  ---> redirect 302
gateway-2   ["www.other.com"]   17d   ---> redirect 302
gateway-3   ["other.de"]       17d  ---> redirect 302

I think this is not optimal. Can I have just one Gateway and two HTTPRoute like this:

node-1:~$ kubectl -n wordpress get Gateway
NAME        CLASS             ADDRESS         PROGRAMMED   AGE
gateway-0   internet-public   192.168.250.4   True         17d ---> all domains in listeners, tls: Terminate, cert-manager created cert

    listeners:
      - name: http
        port: 80
        protocol: HTTP
        hostname: www.site.com
        allowedRoutes:
          namespaces:
            from: All
      - name: https-0
        hostname: www.site.com
        port: 443
        protocol: HTTPS
        allowedRoutes:
          namespaces:
            from: All
        tls:
          mode: Terminate
          certificateRefs:
            - name: www-site-com
      - name: https-0
        hostname: site.com
        port: 443
        protocol: HTTPS
        allowedRoutes:
          namespaces:
            from: All
        tls:
          mode: Terminate
          certificateRefs:
            - name: site-com
etc.

httproutes:
# first HTTPRoute
  - hostnames:
      - www.site.com
    parentRefs:
      - kind: Gateway
        name: gateway-0
    rules:
      - matches:
          - path:
              type: PathPrefix
              value: /
        backendRefs:
          - group: ""
            kind: Service
            name: wordpress
            port: 80
# second HTTPRoute
  - hostnames:
      - site.com
      - www.other.com
      - other.com
    parentRefs:
      - kind: Gateway
        name: gateway-0
    rules:
      - filters:
          - type: RequestRedirect
            requestRedirect:
              hostname: www.site.com
              statusCode: 301

I'm not familiar with the new Gateway API. Just looking for input how to do that property. It should work like this?

[devent]

It works fine like this. I now have 1 gateway with multiple listeners. And 2 HTTPRoute with one have backend ref to the Wordpress service, and the other do a 302 redirect to the main domain.

gateway-0   internet-public   192.168.250.4   True         94s

httproute-0   ["www.site.de"]                                                        3m4s
httproute-1   ["site.de","www.site-other.de","site-other.de"]   3m4s