Kubernetes ingress rules: How to use wildcard and specific subdomain together

9/14/2018

I want Ingress to redirect a specific subdomain to one backend and all others to other backend. Basically, I want to define a rule something like the following:

If subdomain is foo.bar.com then go to s1, for all other subdomains go to s2

When I define the rules as shown below in the Ingress spec, I get this exception at deployment:

Error: UPGRADE FAILED: cannot re-use a name that is still in use

When I change *.bar.com to demo.bar.com it works, however.

Here's my Ingress resource spec:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test
spec:
  rules:
  - host: foo.bar.com
    http:
      paths:
      - backend:
          serviceName: s1
          servicePort: 80
  - host: *.bar.com
    http:
      paths:
      - backend:
          serviceName: s2
          servicePort: 80

Anyone has an idea if it is possible or not?

-- fyelci
kubernetes
kubernetes-ingress
traefik
traefik-ingress

2 Answers

9/14/2018

I'm pretty sure this is currently not possible when looking at Issue 41881, but I could be missing something in the most recent version of Kubernetes—we're about to release 1.12 as we speak.

-- Michael Hausenblas
Source: StackOverflow

4/16/2019

THere is already a PR raised for supporting the wild card domains in ingress rules. refer the below link

https://github.com/containous/traefik/issues/3884

Can you try Traefik v1.7 and see if the wild card support is enabled.

-- P Ekambaram
Source: StackOverflow