When following the EKS GSG instructions to validate Cilium 1.8.0-rc3 for #11903 (including the fix for #12078), the connectivity check for pod-to-b-multi-node-nodeport is failing:
% kubectl get po
NAME READY STATUS RESTARTS AGE
echo-a-58dd59998d-fcfsc 1/1 Running 0 133m
echo-b-865969889d-7qgfg 1/1 Running 0 133m
echo-b-host-659c674bb6-tvzxm 1/1 Running 0 133m
host-to-b-multi-node-clusterip-6fb94d9df6-v25v4 1/1 Running 0 133m
host-to-b-multi-node-headless-7c4ff79cd-2dgct 1/1 Running 0 133m
pod-to-a-5c8dcf69f7-zq2zj 1/1 Running 0 133m
pod-to-a-allowed-cnp-75684d58cc-tb5jm 1/1 Running 0 133m
pod-to-a-external-1111-669ccfb85f-8l2p2 1/1 Running 0 133m
pod-to-a-l3-denied-cnp-7b8bfcb66c-qg2wc 1/1 Running 0 133m
pod-to-b-intra-node-74997967f8-c88x9 1/1 Running 0 133m
pod-to-b-intra-node-nodeport-775f967f47-t426f 1/1 Running 0 133m
pod-to-b-multi-node-clusterip-587678cbc4-xskt6 1/1 Running 0 133m
pod-to-b-multi-node-headless-574d9f5894-xd2jq 1/1 Running 0 133m
pod-to-b-multi-node-nodeport-7944d9f9fc-qpv5r 0/1 Running 0 133m
pod-to-external-fqdn-allow-google-cnp-6dd57bc859-bqhhq 1/1 Running 0 133m
% kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
echo-a ClusterIP 10.100.133.146 <none> 80/TCP 136m
echo-b NodePort 10.100.21.112 <none> 80:31313/TCP 136m
echo-b-headless ClusterIP None <none> 80/TCP 136m
echo-b-host-headless ClusterIP None <none> <none> 136m
kubernetes ClusterIP 10.100.0.1 <none> 443/TCP 147m
% kubectl get ep
NAME ENDPOINTS AGE
echo-a 192.168.108.20:80 136m
echo-b 192.168.98.169:80 136m
echo-b-headless 192.168.98.169:80 136m
echo-b-host-headless 192.168.16.155 136m
kubernetes 192.168.148.188:443,192.168.97.61:443 147m
Follow-up for #12078
/cc @brb
When following the EKS GSG instructions to validate Cilium 1.8.0-rc3 for #11903 (including the fix for #12078), the connectivity check for
pod-to-b-multi-node-nodeportis failing:Follow-up for #12078
/cc @brb