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
Attempted to set up a Kubernetes cluster with version v1.22.9 using a multi-VLAN network and the calico network plugin, as the default canal plugin lacks support for network policies.
The Kubernetes cluster is operational, and an NGINX deployment along with its services has been successfully deployed. However, when attempting to access the services from within the pod, a DNS error is encountered.
Results:
Error in calico-node-* pod logs
bird: BGP: Unexpected connect from unknown address 10.100.0.1 (port 60541)
bird: BGP: Unexpected connect from unknown address 10.100.0.1 (port 43937)
bird: BGP: Unexpected connect from unknown address 10.100.0.1 (port 47457)
bird: BGP: Unexpected connect from unknown address 10.100.0.1 (port 48009)
bird: BGP: Unexpected connect from unknown address 10.100.0.1 (port 47725)
The text was updated successfully, but these errors were encountered:
syedsalman3753
changed the title
RKE1: pod not able to communicate to kubernetes service url for calico network
RKE1: pod not able to communicate to kubernetes service url for calico network [ Not able to resolve host ]
Dec 12, 2024
RKE version: v1.3.10
Docker version: (
docker version
,docker info
preferred)Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred)kernel version
Type/provider of hosts: Bare-metal / KVM is used for VM creation
cluster.yml file:
Steps to Reproduce:
v1.22.9
using a multi-VLAN network and thecalico
network plugin, as the defaultcanal
plugin lacks support for network policies.Results:
calico-node-*
pod logsThe text was updated successfully, but these errors were encountered: