Skip to content
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

Add readiness probe for the vm-runner process #1147

Open
mikhail-sakhnov opened this issue Nov 18, 2024 · 1 comment · May be fixed by #1190
Open

Add readiness probe for the vm-runner process #1147

mikhail-sakhnov opened this issue Nov 18, 2024 · 1 comment · May be fixed by #1190
Assignees
Labels
c/autoscaling/neonvm Component: autoscaling: NeonVM

Comments

@mikhail-sakhnov
Copy link
Contributor

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.

@mikhail-sakhnov mikhail-sakhnov added the c/autoscaling/neonvm Component: autoscaling: NeonVM label Nov 18, 2024
@sharnoff
Copy link
Member

See also #771

@mikhail-sakhnov mikhail-sakhnov linked a pull request Dec 30, 2024 that will close this issue
@mikhail-sakhnov mikhail-sakhnov self-assigned this Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c/autoscaling/neonvm Component: autoscaling: NeonVM
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants