# Ingress subpaths of primary service to separate services

**URL:** <https://discuss.konghq.com/t/ingress-subpaths-of-primary-service-to-separate-services/5699>\
**Category:** Questions\
**Tags:** kubernetes\
**Created:** [March 3, 2020, 2:21pm UTC](https://discuss.konghq.com/t/ingress-subpaths-of-primary-service-to-separate-services/5699 "2020-03-03T14:21:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rparsonsbb](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/rparsonsbb/32/4079_2.png) [@rparsonsbb](https://discuss.konghq.com/u/rparsonsbb)\
**Post date:** [March 3, 2020, 2:21pm UTC](https://discuss.konghq.com/t/ingress-subpaths-of-primary-service-to-separate-services/5699/1 "2020-03-03T14:21:45Z")

</div>

Is it possible to do something like below with kong? Currently it appears that all requests go to the `task` service and `/task/batch` calls won’t actually follow the `/task/batch` path because they’re consumed by the higher level wildcard.

```auto
  rules:
  - host: www.task-doer.com
    http:
      paths:
        - path: /task*
          backend:
            serviceName: task-service
            servicePort: 80
        - path: /task/batch*
          backend:
            serviceName: task-batch-service
            servicePort: 80

```

---

<div class="post-metadata">

**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\
**Post date:** [March 6, 2020, 6:47pm UTC](https://discuss.konghq.com/t/ingress-subpaths-of-primary-service-to-separate-services/5699/2 "2020-03-06T18:47:25Z")

</div>

You can split the rules into two different Ingress resources and then have different regex priorities for them to solve this.