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

DNS resolution stops working when coredns gets restarted #1627

Closed
DevSecNinja opened this issue Nov 13, 2024 · 2 comments · Fixed by #1628
Closed

DNS resolution stops working when coredns gets restarted #1627

DevSecNinja opened this issue Nov 13, 2024 · 2 comments · Fixed by #1628

Comments

@DevSecNinja
Copy link
Contributor

Hey Devin - thanks very much for this awesome template! I ran the template a few years ago with Ubuntu but recently restarted with a simple one node architecture on a Proxmox VM. I noticed a strange issue upon redirecting clients to an auth-url and when coredns gets restarted. I documented the issue and the fix on my GitHub fork and thought you might be interested in potentially also adding this change to the template. I'm not 100 % sure on the impact of this change but I'm not super advanced on Kubernetes. I'll keep an eye out for any strange issues that may arise.

DevSecNinja#962

@onedr0p
Copy link
Owner

onedr0p commented Nov 13, 2024

Looks like a good compatibility change. Please open a PR when you have time, if not soon I can get to it too. Thanks for details into this, it's the first I'm hearing about it.

@DevSecNinja
Copy link
Contributor Author

Thanks - will do! Yeah first time for me too. I was able to find 166 repos with Cilium in Kubesearch and 6 repositories with socketLB.hostNamespaceOnly to true. Bunch of them have Authentik or Authelia set up so I'm curious if others ran into this as well.

image

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

Successfully merging a pull request may close this issue.

2 participants