<p>I have two services, <code>tea</code> and <code>coffee</code>, each is in their own namespace, I would like <code>domain.com</code> to go to the <code>tea</code> service and <code>domain.com/coffee</code> to go to <code>coffee</code>.</p>

<p>As each is in a namespace I have had to make two pieces of ingress, but when I try to apply them I get the error <code>MAPPING   Path '/coffee' already defined in another Ingress rule</code>.</p>

<p>My two pieces of ingress look like the following:</p>

<p>Tea:</p>

<pre><code>kind: Ingress
apiVersion: extensions/v1beta1
spec:
  tls:
  - hosts:
    - domain.com
    secretName: tea-tls
  rules:
  - host: domain.com
    http:
      paths:
      - path: /
        backend:
          serviceName: tea
          servicePort: 80
</code></pre>

<p>and Coffee:</p>

<pre><code>kind: Ingress
apiVersion: extensions/v1beta1
metadata:
  name: coffee
  namespace: coffee
spec:
  tls:
  - hosts:
    - domain.com
    secretName: coffee}-tls
  rules:
  - host: domain.com
    http:
      paths:
      - path: /coffee
        backend:
          serviceName: coffee
          servicePort: 80
      - path: /coffee/*
        backend:
          serviceName: coffee
          servicePort: 80
</code></pre>

<p>I guess the problem isn't having tea and coffee, but defining the <code>coffee</code> path twice in the coffee ingress. According to <a href="https://kubernetes.io/docs/concepts/services-networking/ingress/#simple-fanout" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/services-networking/ingress/#simple-fanout</a> I would assume that you only need the <code>/coffee</code> path, and can delete the <code>/coffee/*</code> path.</p>
