CODEWITHSUNDEEP
kuberneteskubernetes-helmkubernetes-pod
gary69
gary69

Reputation: 4250

Kubernetes ReplicaFailure FailedCreate but no events

I have deployment and a replica set in Kubernetes that are failing to create a pod. I've tried

kubectl describe deployment deployment-name and

kubectl 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?

Upvotes: 30

Views: 36612

Answers (2)

Raunak Kapoor
Raunak Kapoor

Reputation: 931

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

Upvotes: 67

Rico
Rico

Reputation: 61689

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ā“

āœŒļø

Upvotes: 9

Related Questions