We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We don't have any readiness probe for the pod with VM. Some time ago there was readiness probe in case if pod was running through container manager.
I suggest we add readiness probe to avoid having Ready VMs with in fact non-ready runner.
For the readiness probe we could use TCP connection check to vm-daemon and/or postgres process.
The text was updated successfully, but these errors were encountered:
See also #771
Sorry, something went wrong.
No branches or pull requests
We don't have any readiness probe for the pod with VM.
Some time ago there was readiness probe in case if pod was running through container manager.
I suggest we add readiness probe to avoid having Ready VMs with in fact non-ready runner.
For the readiness probe we could use TCP connection check to vm-daemon and/or postgres process.
The text was updated successfully, but these errors were encountered: