Can't access kong manager/admin by domain. These always return "no Route matched with those values"

[yunwz]

I have instaled kic and gateway by helm chart. Show below:

Install cmd:

helm upgrade --install kong kong/ingress --namespace kong --create-namespace  -f ingress-values.yaml

Contant of ingress-values.yaml:

controller: 
  enabled: true
  ingressController:
    enabled: true
    gatewayDiscovery:
      enabled: true
      generateAdminApiService: true
    image:
      repository: kong/kubernetes-ingress-controller
      tag: "3.5"
    env:
      feature_gates: "FillIDs=true"
    #konnect:
    #  license:
    #    enabled: true
    #  enabled: false
    #  controlPlaneID: ""
    #  tlsClientCertSecretName: konnect-client-tls
    #  apiHostname: "us.kic.api.konghq.com"
  podAnnotations:
    kuma.io/gateway: enabled
    # This port must match your Kong admin API port. 8444 is the default.
    # If you set gateway.admin.tls.containerPort, change these annotations
    # to use that value.
    traffic.kuma.io/exclude-outbound-ports: "8444"
    traffic.sidecar.istio.io/excludeOutboundPorts: "8444"

gateway: #gateway 部分用于部署Kong网关
  enabled: true #default value
  image:
    repository: kong/kong
    tag: "3.9.1"
  admin:
    enabled: true
    type: LoadBalancer
    http:
      enabled: true
    tls:
      enabled: true
    ingress:
      tls: true
      enabled: true
      #ingressClassName:
      hostname: "k-admin.mydomain.io"
      path: /
      pathType: Prefix
  manager:
    enabled: true
    type: LoadBalancer
    http:
      enabled: true
    tls:
      enabled: true
    ingress:
      enabled: true
      #ingressClassName:
      hostname: "k-manager.mydomain.io"
      path: /
      pathType: Prefix
  env:
    konnect_mode: "off"
    vitals: "on"
    #cluster_mtls: pki
    #cluster_telemetry_endpoint: ":443"
    #cluster_telemetry_server_name: ""
    #cluster_cert: /etc/secrets/konnect-client-tls/tls.crt
    #cluster_cert_key: /etc/secrets/konnect-client-tls/tls.key
    lua_ssl_trusted_certificate: system
    proxy_access_log: "off"
    dns_stale_ttl: "3600"
    router_flavor: "traditional"
    database: postgres
    pg_host: pg-postgresql.postgre.svc.cluster.local
    pg_port: 5432
    pg_password: kong123
    pg_database: kong_db
    pg_schema: public
    plugins: "bundled"
    #admin_listen: "192.168.10.108:30965 http2 ssl"
  resources:
    requests:
      cpu: 1
      memory: "1Gi"

helm chart info:

$ helm -n kong list
NAME	NAMESPACE	REVISION	UPDATED                             	STATUS  	CHART         	APP VERSION
kong	kong     	8       	2025-08-31 12:39:02.902945 +0800 CST	deployed	ingress-0.21.0	3.9

In kong namespace, svc list:

$ kubectl -n kong get svc
NAME                                 TYPE           CLUSTER-IP      EXTERNAL-IP      PORT(S)                         AGE
kong-controller-metrics              ClusterIP      10.96.144.154   <none>           10255/TCP,10254/TCP             13h
kong-controller-validation-webhook   ClusterIP      10.96.236.66    <none>           443/TCP                         13h
kong-gateway-admin                   LoadBalancer   10.96.115.178   192.168.10.144   8001:32651/TCP,8444:32709/TCP   13h
kong-gateway-manager                 LoadBalancer   10.96.202.39    192.168.10.145   8002:32049/TCP,8445:32657/TCP   13h
kong-gateway-proxy                   LoadBalancer   10.96.119.100   192.168.10.143   80:32073/TCP,443:32252/TCP      13h

ingress list:

$ kubectl -n kong get ingress
NAME                   CLASS    HOSTS                ADDRESS   PORTS   AGE
kong-gateway-admin     <none>   k-admin.mydomain.io               80      13h
kong-gateway-manager   <none>   k-manager.mydomain.io             80      13h

After installing kong successfully, I try to access kong manager by k-manager.mydomain.io, but failed:

when acess kong admin by k-admin.mydomain.io, same output:

Also, I can access kong manager/admin by ip, like these:

I don't have any idea to fix this problem. Does anyone could help me?