Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
s
straight-lunch-71206
12/20/2022, 3:39 PMHello, I'm having an issue where pods can not talk to each other inside the same (custom) namespace. This occurs with CIS enabled or disabled, so I don't think its network policy related. Also I can deploy the same pods to kube-system and they work fine. Am I missing something like a label or annotation that is required for namespaces? Using version v1.24.8+rke2r1
Nodes are ubuntu 20.04 with cis and fips applied.
Using default canal cni, vsphere, all nodes are in the same subnet
c
creamy-pencil-82913
12/20/2022, 6:00 PMWhat you’re saying doesn’t make sense as being due to anything other than network policy
there is nothing other than network policy that would block communication between pods