Both Ingress and Gateway enabled but Ingress not working

I have a customer with a cluster that has installed the helm chart and the values file shows that both the Gateway API and Ingress are enabled

ingressClass:
  enabled: true
  isDefaultClass: true
providers:
  kubernetesCRD:
    allowCrossNamespace: false
    allowEmptyServices: false
    allowExternalNameServices: false
    enabled: true
    namespaces: []
  kubernetesIngress:
    allowEmptyServices: false
    allowExternalNameServices: false
    enabled: true
    namespaces: []
    publishedService:
      enabled: false

But ingress objects creates with the matching ingressClassName do not appear to being routed at all (returning 404 errors).

Manually creating IngressRoute objects for the same hostname/routes works as expected, but the solution doesn't currently support Gateway API (still waiting on proper sticky session support GEP-1619: Session Persistence | Gateway API )

Is this a known issue with a specific version (still waiting for confirmation of what version they have installed). Or any suggestions on how to debug this?

Is there anything else I should be looking at in the values file that might impact this?

Thanks