mac helm deploy pod pod keeps restarting

Based on the information provided in the extracts, there could be several reasons why your pod keeps restarting when deploying Airbyte on Kubernetes using Helm on MacOS. 1. Incompatible Airbyte and Helm Chart versions: As discussed in the [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1676036101206369), there could be an incompatibility between the Airbyte version and the Helm chart version you're using. This was specifically mentioned in the context of the

airbyte-pod-sweeper

not functioning correctly, but it could potentially affect other aspects of the deployment as well. 2. Issues with the

airbyte-webapp

pod: As mentioned in the [forum discussion](https://discuss.airbyte.io/t/4393), there was an issue with the

airbyte-webapp

pod crashing due to an unknown "airbyte_version" variable. The user resolved this by using a different Helm chart version. 3. Resource allocation issues: In the [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1677232488544179), a user experienced issues with setting up connectors, which was initially suspected to be due to insufficient resource allocation. 4. Configuration issues: As discussed in the [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1670494309915759), there could be issues with the configuration of the Helm chart, such as missing default resource limits. To troubleshoot, you could try the following steps: - Check the logs of the restarting pod to identify any error messages. - Ensure that you're using compatible versions of Airbyte and the Helm chart. - Check your resource allocation and adjust if necessary. - Review your Helm chart configuration for any potential issues. If you're still experiencing issues, you might want to wait for the next Helm chart update or reach out to the Airbyte community for further assistance.

---- ------ ---- ---- ------- Normal Scheduled 2m54s default-scheduler Successfully assigned default/airbyte-airbyte-api-server-588bb69ff5-btsnw to minikube Normal Killing 112s kubelet Container airbyte-api-server failed liveness probe, will be restarted Normal Pulled 111s (x2 over 2m51s) kubelet Container image "airbyte/airbyte-api-server:0.50.25" already present on machine Normal Created 111s (x2 over 2m50s) kubelet Created container airbyte-api-server Normal Started 110s (x2 over 2m49s) kubelet Started container airbyte-api-server Warning Unhealthy 73s (x7 over 2m33s) kubelet Readiness probe failed: Get "http://10.244.0.131:8006/health": dial tcp 10.244.0.1318006 connect: connection refused Warning Unhealthy 73s (x3 over 2m13s) kubelet Liveness probe failed: Get "http://10.244.0.131:8006/health": dial tcp 10.244.0.1318006 connect: connection refused Warning Unhealthy 32s (x3 over 112s) kubelet Liveness probe failed: Get "http://10.244.0.131:8006/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 22s (x5 over 112s) kubelet Readiness probe failed: Get "http://10.244.0.131:8006/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers)