Summary
After upgrading to Airbyte version 1.2.0 OSS, the test connection functionality fails in a Kubernetes deployment. A pod is created during the connection check, but health checks are only successful during the connection check process. User requests guidance on potential changes and troubleshooting steps.
Question
Hey Team, we just upgraded to 1.2.0 OSS version, and test connection seems to stop working? we are deployed on Kubernetes… Any pointers what changed and where to look for?
As before I see that a pod gets created when connection check is done, check health is OK only when we are checking connection…
I’ve loaded the POD directly and did a port-forward to eliminate the DNS question and I can confirm that something changed on the Airbyte that causes this to fail… Any advice?
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.