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
I have enabled EKS auto mode on an existing cluster. Some pods fail due to unable to connect to any of endpoints. Hosts names can be resolved because the error is Could not connect to the endpoint URL: "https://secretsmanager.eu-west-2.amazonaws.com/" . Other pods on the same node work normally. Recreating pods helps. I see no pattern in this network issue - I can not relate it to subnet, node, application.
I found that IP addresses of problematic pods are not reflected in ENI secondary IP addresses.
Kubernetes version 1.29, 1.30, 1.31 (upgrading did not help) . Environment AWS eu-west-2.
I tried to find errors in kubectl events and aws ec2 get-console-output - no clue.
The text was updated successfully, but these errors were encountered:
I have enabled EKS auto mode on an existing cluster. Some pods fail due to unable to connect to any of endpoints. Hosts names can be resolved because the error is
Could not connect to the endpoint URL: "https://secretsmanager.eu-west-2.amazonaws.com/"
. Other pods on the same node work normally. Recreating pods helps. I see no pattern in this network issue - I can not relate it to subnet, node, application.I found that IP addresses of problematic pods are not reflected in ENI secondary IP addresses.
Kubernetes version 1.29, 1.30, 1.31 (upgrading did not help) . Environment AWS eu-west-2.
I tried to find errors in
kubectl events
andaws ec2 get-console-output
- no clue.The text was updated successfully, but these errors were encountered: