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

Filtering Ingresses by class #36

Open
cubic3d opened this issue Jul 6, 2021 · 2 comments
Open

Filtering Ingresses by class #36

cubic3d opened this issue Jul 6, 2021 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@cubic3d
Copy link
Contributor

cubic3d commented Jul 6, 2021

Currently it's impossible to filter which Ingress class should be taken into account for polling host names and Loadbalancer IPs.
Example: Two ingress-controllers nginx-int and nginx-ext each having an Ingress resource defining host.domain.tld - the resulting response to the query looks like that:

;; ANSWER SECTION:
host.domain.tld.	60	IN	A	192.168.99.2
host.domain.tld.	60	IN	A	192.168.99.1

But from the internal network (responsibility of the nginx-int controller) only one of those Loadbalancer IPs is accessible on the default port without IP restrictions which leads to timeouts and inability to access the service. Filtering based on ingressClassName and kubernetes.io/ingress.class or some sort of coredns.io/ignore annotation on resources is required to solve that.

@networkop
Copy link
Collaborator

yeah, it makes sense. The original CoreDNS issue had a suggestion for how this could be done. PRs are welcome

@cubic3d
Copy link
Contributor Author

cubic3d commented Aug 6, 2021

I still have an eye on this, just had no time yet ;)

@networkop networkop added enhancement New feature or request help wanted Extra attention is needed labels Aug 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Development

No branches or pull requests

2 participants