Asking for help? Comment out what you need so we can get more information to help you!
Cluster information:
Kubernetes version: 3.4.5
Cloud being used: AWS
Host OS: Linux
Hi All,
Currently, we are encountering an intermittent issue for the request which goes from one POD to another POD for responses. while checking some request gets into timed out state after wait for 2.2 minutes where as some request fired just after the stuck request gets fulfilled.
Error :- I/O error on GET request for "[http://cl0a3567.sunlifecorp.com:34080/dev-hk-empf-dataservice-common/getbusinessdate\": Connection timed out (Connection timed out); nested exception is java.net.ConnectException: Connection timed out (Connection timed out)](http://cl0a3567.sunlifecorp.com:34080/dev-hk-empf-dataservice-common/getDt/": Connection timed out (Connection timed out); nested exception is java.net.ConnectException: Connection timed out (Connection timed out)%22)
But while analyzing the issue, we got to know that POD to POD communication in same worker node can be called using " http:////<basepath" but while using PODS name for calling another POD we are encountering different issue
Error:- Message: 400 Bad Request: [no body]
Please suggest is there anyway we can analyze this issue to fix it as we have tried every possible way to troubleshoot the issue.
Thank you