Missing logs and state after deploying Airbyte in Kubernetes

Summary

After deploying Airbyte in Kubernetes via Helm chart, user is missing logs and state despite successful output to Azure storage account container. Looking for help or troubleshooting documentation.


Question

Hello, I have recently deployed Airbyte community version 1.0.0 in kubernetes via helm chart. After tinkering with some template values, I was able to get the deployment working and storing some output to Azure storage account container, for some reason I am still missing logs and state(?). There is workload/output , so I can confirm that airbyte is in fact able to save stuff to the Azure storage container.
I also checked logs in all the pods and was not able to find any errors that would indicate that there is something wrong with the config / access. Would anyone be able to help me out / point to some troubleshooting documentation



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.

Join the conversation on Slack

["airbyte", "kubernetes", "helm-chart", "azure-storage", "logs", "state", "troubleshooting"]