Summary
User is transitioning from Docker Compose to Kubernetes using Helm Charts and encounters a 502 Bad Gateway error on port 8080 after attempting to load data from a PostgreSQL database. They seek assistance in debugging the issue and migrating data smoothly.
Question
Hi everyone. I previously hosted Airbyte via Docker Compose. Now I’m trying to set up via Kubernetes with Helm Charts. I can get it to run locally on port 8080, but I’m trying to load my data from Docker Compose into the Kubernetes one. I managed to do a pg dump in the VM where I have the Docker Compose version and ingested this pg dump file into DigitalOcean’s Postgres database. I connected to this database from Tableplus - no issues viewing all the data. Then I tried to run helm install again but this time with the values.yaml file containing the Postgres credentials. However, this time, my local port 8080 returns error 502 with http error bad gateway.
Need some assistance on debugging why is this happening, and how can I gracefully migrate all my data from Docker Compose to Kubernetes.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.