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
What happened: Connection to kubernetes service cluster IP from a pod fails with timeout error
connection error
I0822 23:51:24.801068 19 merged_client_builder.go:121] Using in-cluster configuration
I0822 23:51:24.801562 19 round_trippers.go:466] curl -v -XGET -H "Accept: application/json;g=apidiscovery.k8s.io;v=v2;as=APIGroupDiscoveryList,application/json;g=apidiscovery.k8s.io;v=v2beta1;as=APIGroupDiscoveryList,application/json" -H "User-Agent: kubectl/v1.30.3 (linux/amd64) kubernetes/6fc0a69" -H "Authorization: Bearer <masked>" 'https://172.20.0.1:443/api?timeout=32s'
I0822 23:51:54.803543 19 round_trippers.go:508] HTTP Trace: Dial to tcp:172.20.0.1:443 failed: dial tcp 172.20.0.1:443: i/o timeout
I0822 23:51:54.803605 19 round_trippers.go:553] GET https://172.20.0.1:443/api?timeout=32s in 30001 milliseconds
I0822 23:51:54.803619 19 round_trippers.go:570] HTTP Statistics: DNSLookup 0 ms Dial 30001 ms TLSHandshake 0 ms Duration 30001 ms
attempted trace from the node: pod IP(10.0.8.246) starts a connection and the forward packet is seen through conntrack, then nothing... doesnt show up in mangle's prerouting?
kube-proxy(most probably component) has loaded iptables-legacy module into kernel - even if iptables-legacy is not an instal package Warning: iptables-legacy tables present, use iptables-legacy to see them
What you expected to happen: Connection to the KAS
How to reproduce it (as minimally and precisely as possible): just from any pod and sometimes (appears intermittent)
What happened: Connection to kubernetes service cluster IP from a pod fails with timeout error
attempted trace from the node: pod IP(10.0.8.246) starts a connection and the forward packet is seen through conntrack, then nothing... doesnt show up in mangle's prerouting?
![Screenshot 2024-08-22 at 7 04 25 PM](https://private-user-images.githubusercontent.com/56321006/360712622-1976b4ff-446d-45ab-b4f4-4b15e375da3c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNjY4OTQsIm5iZiI6MTczOTI2NjU5NCwicGF0aCI6Ii81NjMyMTAwNi8zNjA3MTI2MjItMTk3NmI0ZmYtNDQ2ZC00NWFiLWI0ZjQtNGIxNWUzNzVkYTNjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDA5MzYzNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQ4YzIyOTM5NjAxMjYyMTJiY2ZkZWQ5ODU1YzU3Yzc2MzFkOGQ0MjgyNDcxM2RmMjRjMGM2N2Y1MjgwNDNlZmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.SEF7Z3lApOahee65yLxwYJmeTO5_bw-aqPyaUqTtVMw)
kube-proxy(most probably component) has loaded iptables-legacy module into kernel - even if iptables-legacy is not an instal package
![Screenshot 2024-08-22 at 7 11 32 PM](https://private-user-images.githubusercontent.com/56321006/360712647-9c37f0ef-6b44-4daf-ac84-5fd4dc1c5795.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNjY4OTQsIm5iZiI6MTczOTI2NjU5NCwicGF0aCI6Ii81NjMyMTAwNi8zNjA3MTI2NDctOWMzN2YwZWYtNmI0NC00ZGFmLWFjODQtNWZkNGRjMWM1Nzk1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDA5MzYzNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTVhODRiNjRiNzViNTdiZGNhMGEyOTIyMWQ5ZTNjOTE1ODEwODQxY2Q0NTFlNjMyNmVmN2NiMjQxYTY3N2JlZjQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.iOlu0UHV12GDkYLZL7f8soKiQmC7kUqV-7xusj-Bisc)
Warning: iptables-legacy tables present, use iptables-legacy to see them
What you expected to happen: Connection to the KAS
How to reproduce it (as minimally and precisely as possible): just from any pod and sometimes (appears intermittent)
Anything else we need to know?:
Environment:
aws eks describe-cluster --name <name> --query cluster.platformVersion
): "eks.20"aws eks describe-cluster --name <name> --query cluster.version
): "1.27"uname -a
): Linux ip-10-0-8-243.us-west-2.compute.internal 6.1.102-108.177.amzn2023.x86_64 Template is missing source_ami_id in the variables section #1 SMP PREEMPT_DYNAMIC Wed Jul 31 10:18:50 UTC 2024 x86_64 x86_64 x86_64 GNU/Linuxcat /etc/eks/release
on a node):The text was updated successfully, but these errors were encountered: