@kapa.ai I have problem in deploy airbyte/server:0.64.1 with helm chart on kubernetes, error:

Readiness probe failed: Get "<http://10.138.14.35:8001/api/v1/health>": dial tcp 10.138.14.35:8001: connect: connection refused
Liveness probe failed: Get "<http://10.138.14.35:8001/api/v1/health>": dial tcp 10.138.14.35:8001: connect: connection refused

I can't read the logs on port 5005 since the service doesn't go up. Do you have a similar problem with a ready-made solution?

Yes, there have been similar issues reported by other users when deploying Airbyte on Kubernetes using Helm charts. The error messages you're seeing are typically related to the readiness and liveness probes failing to connect to the Airbyte server. Here are a few things you can try: 1. Check the status of your pods: Use the

kubectl get pod

command to check the status of your pods. Make sure all the pods are up and running. If any of them are not running, you may need to investigate further. 2. Check your Kubernetes version: Make sure you're running a supported version of Kubernetes. The Helm chart version you're using might not be compatible with your Kubernetes version. 3. Check your resource allocation: There have been issues reported where the deployment fails due to insufficient resources. Make sure your Kubernetes cluster has enough resources to run Airbyte. 4. Check your network configuration: The error messages suggest that the probes are unable to connect to the Airbyte server. This could be due to network configuration issues in your Kubernetes cluster. Unfortunately, without more information, it's hard to provide a more specific solution. If the problem persists, I would recommend opening an issue on the [Airbyte GitHub](https://github.com/airbytehq/airbyte/issues) page with more details about your setup and the exact error messages you're seeing. Sources: - [Github Issue 39913](https://github.com/airbytehq/airbyte/issues/39913) - [Github Issue 40231](https://github.com/airbytehq/airbyte/issues/40231) - [Forum Post 2661](https://discuss.airbyte.io/t/2661) - [Forum Post 4084](https://discuss.airbyte.io/t/4084) - [Airbyte Troubleshooting Guide](https://docs.airbyte.com/deploying-airbyte/troubleshoot-deploy#connection-refused)