Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
c
creamy-pencil-82913
04/20/2023, 5:57 AMOpen an issue on GH and attach as much info as possible, I'll ask the CNI guys to take a look
👍 1
a
adamant-soccer-4302
04/25/2023, 9:52 PMI didn't get to opening a ticket, because shortly after this I identified it was tied to net.ipv4.xfrm4_gc_thresh being too low - increase the number, and the pods that were having issues connecting out to another endpoint suddenly started working
we got the error message 'No buffer space available' when trying to connect to remote services over the ipsec network, but it worked over the host network just fine - cilium was reporting the health endpoint on the worker node was healthy, but the overlay network target was unhealthy over the ipsec network
c
creamy-pencil-82913
04/25/2023, 9:58 PMinteresting. thanks for the follow-up!