You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to deploy flannel v0.26.2 with the default vxlan backend. Afterwards I noticed that I havent had any chance to get dns resolutions or connection to other pods
Expected Behavior
DNS resolution and pod network working
Current Behavior
no dns resolution, no network connection to other pods
I first noticed when I deployed a cloud controller who wants to connect to the api of the provider and this failed every time. When I changed the backend to host-gw it immediatly started working
I now tried to deploy an basic echo server and want to access it but its only working from the node itself. In the flannel logs I can see:
I tried to deploy flannel v0.26.2 with the default vxlan backend. Afterwards I noticed that I havent had any chance to get dns resolutions or connection to other pods
Expected Behavior
DNS resolution and pod network working
Current Behavior
no dns resolution, no network connection to other pods
Possible Solution
I dont have one
Steps to Reproduce (for bugs)
k apply -f https://github.com/flannel-io/flannel/releases/download/v0.26.2/kube-flannel.yml
k apply -f https://k8s.io/examples/admin/dns/dnsutils.yaml
k exec -i -t dnsutils -- nslookup kubernetes.default
Context
I first noticed when I deployed a cloud controller who wants to connect to the api of the provider and this failed every time. When I changed the backend to
host-gw
it immediatly started workingI now tried to deploy an basic echo server and want to access it but its only working from the node itself. In the flannel logs I can see:
Your Environment
kube-flannel-cfg
The text was updated successfully, but these errors were encountered: