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
We have been seeing intermittent 502s with applications hosted on AKS. Upon troubleshooting, it was identified that requests going to particular ingress controller pod is consistently throwing a 502 while others are not. It starts working if that particular pod is restarted. Within the next day or two, either same ingress pod or a different pod behaves the same way. We have enabled debug on the failing pod's kuma-sidecar and noticed it is unable to verify cert with below errors
In some cases, ingress DP certs are valid whereas the application's DP certs are expired. So, it is pretty inconsistent as to which component is consistently having issues. Overall, it is very random across the cluster. Either ingress controller pods restart fixes it or/and application pod restart fixes it.
Environment
Kuma version 2.5.10
AKS 1.28.15 and 1.30.6
Ingress controller version 1.10.3
How to reproduce
Took few days after several attempt so below steps might not work immediately
Install Kuma 2.5.10 and ingress controller 1.10.3 on AKS 1.28.15 or 1.30.6
Deploy a sample app with sidecar injection label
Wait for atleast a day or two and continuously access the application using ingress url and you should see 502s come up intermittently.
The text was updated successfully, but these errors were encountered:
We have other bugs when we upgrade to a version >2.5.10 which we have already opened an issue about. Can you at least give some pointers or related issues for these kind of issues? I have searched this repo and couldn't find any.
What happened?
We have been seeing intermittent 502s with applications hosted on AKS. Upon troubleshooting, it was identified that requests going to particular ingress controller pod is consistently throwing a 502 while others are not. It starts working if that particular pod is restarted. Within the next day or two, either same ingress pod or a different pod behaves the same way. We have enabled debug on the failing pod's kuma-sidecar and noticed it is unable to verify cert with below errors
So, when I looked the dataplaneinsights of this particular dataplane, I see the cert is expired while the DP is still active
In some cases, ingress DP certs are valid whereas the application's DP certs are expired. So, it is pretty inconsistent as to which component is consistently having issues. Overall, it is very random across the cluster. Either ingress controller pods restart fixes it or/and application pod restart fixes it.
Environment
Kuma version 2.5.10
AKS 1.28.15 and 1.30.6
Ingress controller version 1.10.3
How to reproduce
Took few days after several attempt so below steps might not work immediately
The text was updated successfully, but these errors were encountered: