What does "Does not have minimum availability" mean?
A GitHub discussion was found, but it is not clear to me what the error message means.
DevOps Stack Exchange is a question and answer site for software engineers working on automated testing, continuous delivery, service integration and monitoring, and building SDLC infrastructure. It only takes a minute to sign up.Sign up to join this community
As @Tensibai indicated in one the comments, this could be caused as there is unsufficient CPU or memory, but that is not always the case.
For example, a helm chart was just deployed, it failed and the workload in GCP indicated that:
Pod errors: CrashLoopBackOff
Based on the comment of @Tensibai the first impression was that there were insufficient resources, but further analysis using
kubectl describe pod <pod-name> indicated that in this case the livenessProbe check failed:
Liveness probe failed: Get http://10.16.0.13:80/: dial tcp 10.16.0.13:80: getsockopt: connection refused
In summary, the
Does not have minimum availability message is generic. Multiple issues could trigger this and more in dept analysis is required to find the actual error.