-
Notifications
You must be signed in to change notification settings - Fork 474
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PGBouncer Liveness Probe Failure Minikube #558
Comments
I believe this to be a minikube issue. nslookup -type=a airflow-pgbouncer Name: airflow-pgbouncer.airflow.svc.cluster.local nc -vz 10.104.178.111 6432 nc -vz localhost 6432 Not sure how to tackle this one. What am I missing |
@razilevin have you tried with the newly released version I wonder if your problem was fixed by #547. Also, can you do a |
Yes as of last night. No luck. Here are some command outputs. I do see the startup probe as defined in the chart. helm list -n airflow
kubectl describe -n airflow pod airflow-pgbouncer-5cbcc9dfc7-ttpzd
|
@razilevin I just tested this myself, and I CAN reproduce this with minikube We can fix this for chart version Either way, I recommend using something like k3d (what I currently use) or kind, they are both much easier to use than minikube, and don't have this problem. |
@razilevin I have raised PR #560 to fix this issue, which will be part of |
@razilevin the long-awaited Thanks for your help! |
Checks
Chart Version
airflow-8.5.3
Kubernetes Version
Helm Version
Description
For some reason the liveness probe for PGBouncer fails causing restarts. I have execed into the pod and tried to run the command emulating the liveness probe,
It just hangs when using the command as is but replacing the DNS name with localhost the command succeeds.
I have tested K8s DNS and it does resolve to the correct pod IP.
I have tried to follow along with the existing issues related to pgbouncer no luck.
Not sure what else to try.
Relevant Logs
No response
Custom Helm Values
No response
The text was updated successfully, but these errors were encountered: