Skip to content
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.

Ingress component does not work with external-dns to create DNS entries based on Ingress objects #13

Closed
2 tasks
invidian opened this issue Feb 5, 2020 · 1 comment
Labels
blocked Blocked by other issue

Comments

@invidian
Copy link
Member

invidian commented Feb 5, 2020

Currently as Ingress Controller implementation, we use Contour, which at the moment does not set the IP value in Ingress resources, which makes it unusable with external-dns component.

Example:

$ kubectl get ingress --all-namespaces
NAMESPACE   NAME      HOSTS                                    ADDRESS   PORTS     AGE
dex         dex       dex.london.lokomotive-k8s.net                 80, 443   23h
gangway     gangway   gangway.london.lokomotive-k8s.net             80, 443   23h

This has been a long standing issue for Contour (projectcontour/contour#403) from 2018.

Workarounds

  • use Envoy annotations and configure external-dns to also create entries based on Service objects annotations
  • Create alternative implementation for Ingress component using e.g. nginx-ingress and recommend using that if user needs external-dns integration

Actual solution

We could join efforts in projectcontour/contour#2121 and implement this functionality in Contour.

@invidian
Copy link
Member Author

invidian commented Jun 9, 2020

We added a workaround for it in 71c19e0, but it is no longer needed, so it should be removed as stated in #589. Nothing to do here.

@invidian invidian closed this as completed Jun 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked Blocked by other issue
Projects
None yet
Development

No branches or pull requests

1 participant