# Kong route is ignored

**URL:** <https://discuss.konghq.com/t/kong-route-is-ignored/10698>\
**Category:** Questions\
**Tags:** kubernetes\
**Created:** [September 23, 2022, 3:35pm UTC](https://discuss.konghq.com/t/kong-route-is-ignored/10698 "2022-09-23T15:35:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hoisu](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hoisu/32/3647_2.png) [@hoisu](https://discuss.konghq.com/u/hoisu)\
**Post date:** [September 23, 2022, 3:35pm UTC](https://discuss.konghq.com/t/kong-route-is-ignored/10698/1 "2022-09-23T15:35:48Z")

</div>

I’m trying to setup Kong in Kubernetes. While following the official documentation from [Using KongIngress resource - Kong Ingress Controller - v2.6.x | Kong Docs](https://docs.konghq.com/kubernetes-ingress-controller/2.6.x/guides/using-kongingress-resource/) I’m, unable to make it work. Every request I make to the URL it ends up with no route.

```auto
curl -X GET https://<$PROXY_IP>/<service_name> -L
{"message":"no Route matched with those values"}%

```

Kong logs don’t throw any errors and I can see the route and service in Kong admin. My k8s objects are the following

```auto
    Ingress Config:
    kind: Ingress
    metadata:
      annotations:
        konghq.com/override: <service_name>
        meta.helm.sh/release-name: <service_name>
        meta.helm.sh/release-namespace: services
      creationTimestamp: "2022-09-23T14:03:05Z"
      generation: 1
      labels:
        app.kubernetes.io/managed-by: Helm
      name: <service_name>
      namespace: <service_ns>
      resourceVersion: "18823478"
      uid: 10f15c94-0c56-4d27-b97d-0ad5bdd549ec
    spec:
      ingressClassName: kong
      rules:
      - http:
          paths:
          - backend:
              service:
                name: <service_name>
                port:
                  number: 8080
            path: /<service_name>
            pathType: ImplementationSpecific
    status:
      loadBalancer:
        ingress:
        - ip: 172.16.44.236

```

```auto
apiVersion: configuration.konghq.com/v1
kind: KongIngress
metadata:
  annotations:
    meta.helm.sh/release-name: <service_name>
    meta.helm.sh/release-namespace: services
  creationTimestamp: "2022-09-23T14:03:05Z"
  generation: 1
  labels:
    app.kubernetes.io/managed-by: Helm
  name: <service_name>
  namespace: services
  resourceVersion: "18823487"
  uid: 9dd47a3c-598a-48fe-ba60-29779156b58d
route:
  methods:
  - GET
  strip_path: true

```

```auto
apiVersion: v1
kind: Service
metadata:
  annotations:
    cloud.google.com/neg: '{"ingress":true}'
    konghq.com/override: <service_name>
    meta.helm.sh/release-name: <service_name>
    meta.helm.sh/release-namespace: services
  creationTimestamp: "2022-09-23T14:03:04Z"
  labels:
    app.kubernetes.io/instance: <service_name>
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: <service_name>
    app.kubernetes.io/version: latest
    helm.sh/chart: <local_chart>
  name: authenticate
  namespace: services
  resourceVersion: "18820083"
  uid: a3112c22-4df7-40b0-8fd3-cde8516354cc
spec:
  clusterIP: 172.16.45.71
  clusterIPs:
  - 172.16.45.71
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - name: http
    port: 8080
    protocol: TCP
    targetPort: 8080
  selector:
    app.kubernetes.io/instance: <service_name>
    app.kubernetes.io/name: <service_name>
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

```

I’m battling this issue for days now and I can’t seem to figure it out.

---

<div class="post-metadata">

**Author:** ![traines](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/traines/32/158_2.png) [@traines](https://discuss.konghq.com/u/traines)\
**Post date:** [September 28, 2022, 11:43pm UTC](https://discuss.konghq.com/t/kong-route-is-ignored/10698/2 "2022-09-28T23:43:38Z")

</div>

Does `kubectl logs PODNAME -c ingress-controller` show any errors pushing configuration? Does the route you see in the admin API actually look correct?

Can you provide the route from the admin API, with the actual path in it and the request? Usually once it’s showing up there you should be fine; if it’s not matching that should indicate that the path or some other aspect isn’t actually correct for the request you’re making, and that’s not possible to diagnose with only placeholder values.