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 insufficient 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.
Just want to throw out an example of it not being the CPU / mem.
I remade a cluster, which included a new node pool, nodes, etc. Then tried re-deploying some of the pods that were on the previous cluster. 3 of them were working, and one kept showing "Does not have minimum availability".
It turns out, the pod in question's deployment file had
spec.template.spec.nodeName hard-coded to one of the nodes from the previous cluster. In the new cluster, that node does not exist, so it failed.
Review your k8s deployment file (.yaml or .json) if you are running into this issue and the other solutions don't work. Maybe even service files as well.
I have faced a similar error for my Gitlab runner deployment on the GKE cluster. As you can see from the error, something is wrong with our pods. Why shouldn't we go and check the pod status?
kubectl describe pods -n namespace
You will get a fair idea about what's the real issue behind the error “Does not have minimum availability”.
In my case, the node was unable to pull the image for my deployment from the google container registry (GCR). I checked the permission for the service account used for k8s-cluster to pull the images from GCR.
I provided the correct roles and then it worked. Roles: