Summary
Users are encountering a 502 error when trying to access Airbyte deployed in EKS using Argo CD. The error seems to be related to connection resets by the upstream server.
Question
Hi Team, i am trying to get the latest helm chart(0.58.18) deployed in eks using argo cd. Deployment is all fine, getting below error while accessing airbyte( errors from webapps pod posted), all other pods/services are health, appreciate if someone assist me please.
127.0.0.6 - - [21/Mar/2024:06:39:05 +0000] "GET /api/v1/instance_configuration HTTP/1.1" 502 497 "<https://airbyte-temp.dev.moxehealth.com/>" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:123.0) Gecko/20100101 Firefox/123.0" "10.92.40.144"
2024/03/21 06:39:05 [error] 37#37: *43 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.6, server: localhost, request: "GET /api/v1/instance_configuration HTTP/1.1", upstream: "<http://172.20.194.149:8001/api/v1/instance_configuration>", host: "<http://airbyte-temp.dev.moxehealth.com|airbyte-temp.dev.moxehealth.com>", referrer: "<https://airbyte-temp.dev.moxehealth.com/>"
2024/03/21 06:39:09 [error] 37#37: *43 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.6, server: localhost, request: "GET /api/v1/instance_configuration HTTP/1.1", upstream: "<http://172.20.194.149:8001/api/v1/instance_configuration>", host: "<http://airbyte-temp.dev.moxehealth.com|airbyte-temp.dev.moxehealth.com>", referrer: "<https://airbyte-temp.dev.moxehealth.com/>"
127.0.0.6 - - [21/Mar/2024:06:39:09 +0000] "GET /api/v1/instance_configuration HTTP/1.1" 502 497 "<https://airbyte-temp.dev.moxehealth.com/>" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36" "10.92.40.173"
127.0.0.6 - - [21/Mar/2024:06:39:10 +0000] "GET /index.html HTTP/1.1" 200 17137 "-" "kube-probe/1.29+" "-"
2024/03/21 06:39:14 [error] 37#37: *43 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.6, server: localhost, request: "GET /api/v1/instance_configuration HTTP/1.1", upstream: "<http://172.20.194.149:8001/api/v1/instance_configuration>", host: "<http://airbyte-temp.dev.moxehealth.com|airbyte-temp.dev.moxehealth.com>", referrer: "<https://airbyte-temp.dev.moxehealth.com/>"
127.0.0.6 - - [21/Mar/2024:06:39:14 +0000] "GET /api/v1/instance_configuration HTTP/1.1" 502 497 "<https://airbyte-temp.dev.moxehealth.com/>" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:123.0) Gecko/20100101 Firefox/123.0" "10.92.40.144"
2024/03/21 06:39:21 [error] 37#37: *43 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.6, server: localhost, request: "GET /api/v1/instance_configuration HTTP/1.1", upstream: "<http://172.20.194.149:8001/api/v1/instance_configuration>", host: "<http://airbyte-temp.dev.moxehealth.com|airbyte-temp.dev.moxehealth.com>", referrer: "<https://airbyte-temp.dev.moxehealth.com/>"
127.0.0.6 - - [21/Mar/2024:06:39:21 +0000] "GET /api/v1/instance_configuration HTTP/1.1" 502 497 "<https://airbyte-temp.dev.moxehealth.com/>" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36" "10.92.40.173"
2024/03/21 06:39:25 [error] 37#37: *43 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.6, server: localhost, request: "GET /api/v1/instance_configuration HTTP/1.1", upstream: "<http://172.20.194.149:8001/api/v1/instance_configuration>", host: "<http://airbyte-temp.dev.moxehealth.com|airbyte-temp.dev.moxehealth.com>", referrer: "<https://airbyte-temp.dev.moxehealth.com/>"
127.0.0.6 - - [21/Mar/2024:06:39:25 +0000] "GET /api/v1/instance_configuration HTTP/1.1" 502 497 "<https://airbyte-temp.dev.moxehealth.com/>" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:123.0) Gecko/20100101 Firefox/123.0" "10.92.40.144"```
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1711003379736969) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
["error-502", "accessing-airbyte", "eks", "argo-cd", "502-error", "connection-reset"]
</sub>