-
Notifications
You must be signed in to change notification settings - Fork 4
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
service available replicas below target #33
Comments
Interesting, once I bounced the akash-provider, that lease terminated due to
|
And that lease looked okay, i.e. did not get overdrawn, was running for less than 2 days:
|
This can happen when the docker container is unavailable, or has an error in it. Is it possible |
Could be, I've entirely forgot to check the pod itself. |
haven't seen these messages for quite some time. |
FWIW, the More details: In Akash deployments, the process involves converting the deployment into the Kubernetes (K8s)
When the (
I.e. the incrementing
|
akash v0.16.4
I'm often seeing providers to hit
service available replicas below target
message despite the pod/svc/ing seem to be running well.Related code path https://github.com/ovrclk/akash/blob/v0.16.4/provider/cluster/monitor.go#L185
provider logs
The text was updated successfully, but these errors were encountered: