-
Notifications
You must be signed in to change notification settings - Fork 587
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
CoreDNS pods are not rechable for resolution from other node #3388
Comments
After applying fix from projectcalico/calico#3145 DNS resolution works cross nodes.
|
Is it reboot proof? I upgraded k8s to latest 1.26.4, and it still reoccurring. |
@rancher/rke1-team According to projectcalico/calico#3145 (comment), there is a patched kernel and an environment variable that can be configured to work-around this. Do we need to add this to the next KDM template? |
What CNI plugin are you using? |
@manuelbuil We used default installation so canal plugin.
I've noticed very similar issue reported for RKE2 https://docs.rke2.io/known_issues/#calico-with-vxlan-encapsulation @kagipra disabling offloading via ethtool is not reboot persistent. |
This is occurring for me as well for a brand new Ubuntu 22 cluster - and the workaround suggested does work. |
This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions. |
RKE version:
rke version v1.4.8
Docker version: (
docker version
,docker info
preferred)Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred)Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
vmware
cluster.yml file:
Steps to Reproduce:
Results:
Firewalld is disabled
Resolution is working fine locally on same server, doesn't work against pod on another node, and via service IP it's taking long time
SURE-6954
The text was updated successfully, but these errors were encountered: