Kubernetes ReplicaFailure FailedCreate but no events
Solution 1
I believe the docs are pretty clear π on how to debug this. This is a 'failed' deployment and possible causes:
- Insufficient quota
- Readiness probe failures
- Image pull errors
- Insufficient permissions
- Limit ranges
- Application runtime misconfiguration
You can try to debug for example by patching the progressDeadlineSeconds
deployment spec field to something long.
kubectl patch deployment.v1.apps/deployment-name -p '{"spec":{"progressDeadlineSeconds":600}}'
Maybe you have a ReplicaSet resource quotaβ
βοΈ
Solution 2
Describe replicaset will give you the error that is causing failure with deployment object.
./kubectl describe replicaset <replica-set-name>
Example error:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal SuccessfulCreate 13m replicaset-controller Created pod: pod
Warning FailedCreate 13m replicaset-controller Error creating: pods "pod" is forbidden: exceeded quota: custom-resource-quota, requested: cpu=510m, used: cpu=1630m, limited: cpu=2
Related videos on Youtube

gary69
Updated on September 23, 2020Comments
-
gary69 about 2 years
I have deployment and a replica set in Kubernetes that are failing to create a pod. I've tried
kubectl describe deployment deployment-name
andkubectl describe replicaset replicaset-name
And they both say
Conditions: Type Status Reason ---- ------ ------ ReplicaFailure True FailedCreate Events: <none>
All of the troubleshooting guides I've seen rely on information from the Events section but it says
<none>
in my case. How can I get more information to debug the problem?-
Tarun Khosla over 2 yearsShare your yaml
-
-
gary69 over 2 yearsThank you, I was exceeding the CPU resource quota. I was able to see the error when viewing the Replica Set json from the UI