Symptoms¶
- A new deployment
notification-servicein namespacestagingis stuck at 0 available replicas. kubectl get deployment notification-service -n stagingshows0/3ready.- The ReplicaSet has been created but no pods appear.
kubectl get pods -n staging -l app=notification-servicereturns no results.- The deployment manifest is valid and works in the
devnamespace. - The
stagingnamespace has a ResourceQuota applied. - Events on the ReplicaSet show a quota error.