<p>I have a domain at Cloudflare and some wildcards for subdomains</p>
<p><a href="https://i.stack.imgur.com/R46FF.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/R46FF.png" alt="enter image description here" /></a></p>
<p>which both point to the load balancer of an nginx ingress of a Kubernetes cluster (GKE) of the GCP. Now, we have two pods and services running each (echo1 and echo2, which are essentially identical) and when I apply an ingress</p>
<pre><code>kind: Ingress
metadata:
  name: echo-ingress
  annotations:
    kubernetes.io/ingress.class: &quot;nginx&quot;
    nginx.ingress.kubernetes.io/ssl-redirect: &quot;false&quot;
spec:
  rules:
  - host: &quot;echo1.eu3.example.com&quot;
    http:
        paths:
        - pathType: Prefix
          path: &quot;/&quot;
          backend:
            service:
              name: echo1
              port:
                number: 80
  - host: &quot;echo2.example.com&quot;
    http:
        paths:
        - pathType: Prefix
          path: &quot;/&quot;
          backend:
            service:
              name: echo2
              port:
                number: 80
</code></pre>
<p>I can reach echo2 under echo2.example.com, but not echo1.eu3.example.com. My question is how I can make the second one reachable as well.</p>

<p>I can advise you to make some check.</p>
<p>Just set the Proxy status for &quot;echo1.eu3.example.com&quot; as DNS only. Then check the access. If ok - install certificates in kubernetes via cert manager. We faced some times with this issue and resolved by using 3 deep domains. For instance &quot;echo1-eu3.example.com&quot;. It seems cloudfront does not like such domains :) Of course if someone write a solution how to work with deep domains in cloudfront - it would be good practice for us :)</p>
