Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

External CNAME records do not route properly via hostnames #404

Closed
buckhx opened this issue Jul 18, 2018 · 1 comment
Closed

External CNAME records do not route properly via hostnames #404

buckhx opened this issue Jul 18, 2018 · 1 comment

Comments

@buckhx
Copy link

buckhx commented Jul 18, 2018

Using CNAME records to route to services via hostnames does not work. With the following setup, dev.test.io will 404. Changing the records to both be A records in the external DNS pointing to the same static IP routes properly with the same Ingress definition.

Example Zones:

test.io            A              <static-ip-of-glb>
dev.test.io     CNAME    test.io 

Example Ingress:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: gateway
  namespace: dev 
  annotations:
    kubernetes.io/ingress.class: gce 
spec:
  tls:
  - hosts:
    - dev.test.io
    - test.io
  rules:
  - host: test.io
    http:
      paths:
      - path: /
        backend:
          serviceName: web 
          servicePort: 80
  - host: dev.test.io
    http:
      paths:
      - path: /
        backend:
          serviceName: web-dev
          servicePort: 80
@buckhx
Copy link
Author

buckhx commented Jul 18, 2018

Looks like it was a separate issue, pls ignore.

@buckhx buckhx closed this as completed Jul 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant