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
This is not a security vulnerability or a crashing bug
This is not a question about how to use Istio
Bug Description
I am using the AWS EKS kubernetes version 1.27 and istio version 1.20.6, and i am using the karpenter as node autoscaler
i had upgraded istio from 1.15.2 to 1.20.6, in both istio version issue is same
issue i am getting is, when karpenter is draining the node called as consolidation, istio is sending the request to draining node and request to pod for which istio is sending is and was not available on that node, when we are making consolidation=false, then we are not getting the issue, we are using the AMI family as bottlerocket, and the request which istio had send to application is running fine with 3 replicas in different nodes, and all pod are running fine at that time and i am getting 504 error.
can someone help me to apply which config i have to change.
installation command
navneet-we
changed the title
istio is sending request of application to node on which application is no scheduled in its lifetime.
istio is sending request of application to node on which application is no scheduled in its lifetime and getting 504
May 16, 2024
Is this the right place to submit this?
Bug Description
I am using the AWS EKS kubernetes version 1.27 and istio version 1.20.6, and i am using the karpenter as node autoscaler
i had upgraded istio from 1.15.2 to 1.20.6, in both istio version issue is same
issue i am getting is, when karpenter is draining the node called as consolidation, istio is sending the request to draining node and request to pod for which istio is sending is and was not available on that node, when we are making consolidation=false, then we are not getting the issue, we are using the AMI family as bottlerocket, and the request which istio had send to application is running fine with 3 replicas in different nodes, and all pod are running fine at that time and i am getting 504 error.
can someone help me to apply which config i have to change.
installation command
istioctl install --revision=1-20-6 --set profile=default --set hub=361428600572.dkr.ecr.ap-south-1.amazonaws.com --skip-confirmation
Version
Additional Information
No response
The text was updated successfully, but these errors were encountered: