-
Notifications
You must be signed in to change notification settings - Fork 275
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 over TLS not working #5550
Milestone
Comments
This was referenced Mar 5, 2024
Merged
Validated on master branch with commit c7cd05bEnvironment/Config
Testing stepsThanks to Manuel for the detailed steps Replication:
Validation:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environmental Info:
RKE2 Version:
RKE2 February release: v1.29.2, v1.28.7, v1.27.11, v1.26.14
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
Describe the bug:
When using a TLS config in coredns, we get an error in the logs of coredns:
The reason is that the path
ls /etc/ssl/certs
is empty and it should contain the typical CA certificates.Steps To Reproduce:
1 - Deploy RKE2 (e.g.
v1.29.2+rke2r1
)2 - Check the logs on coredns: (e.g.
kubectl logs rke2-coredns-rke2-coredns-6fd7bb5597-4b5kn -n kube-system
)3 -
kubectl edit cm rke2-coredns-rke2-coredns -n kube-system
4 - Replace
forward . /etc/resolv.conf\n
byforward . tls://1.1.1.1:853 tls://1.0.0.1:853\n
5 - Consume the new config:
kubectl rollout restart deployment rke2-coredns-rke2-coredns -n kube-system
6 - Wait for pods to come up. Once they are up, check the logs. You should see the problem:
Expected behavior:
No error
Actual behavior:
Error which makes it impossible to reach DNS servers using TLS
Additional context / logs:
The text was updated successfully, but these errors were encountered: