IssueTracker

Hello,

Thanks for reaching out to us!

The Product Engineering Team has been made aware of your feature request, and will address it in due course. Though we can't provide an ETA on feature requests nor guarantee their implementation, rest assured that your feedback is always taken very seriously, as it allows us to improve our products. Thank you for your trust and continued support to improve Google Cloud Platform products.

In case you want to report a new issue, please do not hesitate to create a new Issue Tracker thread describing your issue. Once again, thank you for the suggestions.

Thanks & Regards,
Manish Bavireddy.
Google Cloud Support

Hi,

Thanks for your response.

The information has been shared with the Product Team and further updates will be provided in this thread.

According to the Public Issue Tracker Process, we wait for a bug to gain a handful of stars, and hopefully, comments from several users before the engineering team works on the issue. Though we can't provide an ETA on this issue nor guarantee their implementation, rest assured that your feedback is always taken very seriously.

Please note that the Issue Tracker is primarily meant for reporting bugs and requesting new features. If you have any additional issues or concerns, please don’t hesitate to create a new thread on the Issue Tracker. We appreciate your cooperation!

Thanks

Hello,

we also had the problem of receiving an 404 HTTP Error with the body message 'fault filter abort' whenever a client connects to the gatway with a port inside the 'Host' Header.

For everyone looking for a workaround, try it this way: For every domain, create one HTTPRoute with two matchers for the HTTP Header "Host". One matching "Host" to "domain:port" and one matching "Host" to "domain" without the port.

apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: my-workaround-https-route
spec:
#  hostnames:
#    - "mydomain.com"
  parentRefs:
    - kind: Gateway
      name: my-gateway
      sectionName: https-listener
  rules:
    # This host header matchers are the workaround 
    # Open issue at google (https://issuetracker.google.com/issues/294510336)
    - matches:
        # Matches domain with port
        - headers:
            - name: "Host"
              value: "mydomain.com:443"
          path:
            value: /
            type: PathPrefix
        # Matches domain only
        - headers:
            - name: "Host"
              value: "mydomain.com"
          path:
            value: /
            type: PathPrefix
      # This is not important for the workaround but maybe also useful for people switching from ingress to gateway
      filters:
        - type: RequestHeaderModifier
          requestHeaderModifier:
            set:
              - name: X-Forwarded-Host
                value: "{tls_sni_hostname}"
      backendRefs:
        - name: my-backend-service
          port: 8080

The downside is that you have to create matchers instead of just simply listing all the domains you want to route through this rule. If you use multiple HTTPRoute resources for the same domains, make sure that the rules do not overwrite each other.

I hope the issue gets resolved quickly, we can't implement it on all domains and can't migrate all load balancers to gateway api.