ARTIFACTORY: How To Fix "Failed Quota" and "Exceeded Quota" While Deploying Artifactory-HA in Helm

The purpose of this article is to overcome the "failed quota" and "exceeded quota" warnings that appear in the statefulset and/or replicaset descriptions when deploying the Artifactory-HA Helm chart. In addition to this, other problematic symptoms include missing pods, PVs and PVCs.

I have seen the issue where no Kubernetes (K8s) pods are created in the Helm deployment of Artifactory-HA. When we run "kubectl get all" in the namespace, we see the deployment, replicaset, statefulset, and services are created:

NAME                                            TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
service/artifactory-ha-postgresql-headless      ClusterIP      xxxxxxx            <none>        5432/TCP                     11m
service/artifactory-ha-postgresql               ClusterIP      xxxxxxx    <none>        5432/TCP                     11m
service/artifactory-ha                          ClusterIP      xxxxxxx    <none>        8082/TCP,8025/TCP,8081/TCP   11m
service/artifactory-ha-artifactory-ha-primary   ClusterIP      xxxxxxx   <none>        8082/TCP,8081/TCP            11m
service/artifactory-ha-nginx                    LoadBalancer   xxxxxxx    <pending>     80:30294/TCP,443:31409/TCP   11m

NAME                                   READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/artifactory-ha-nginx   0/1     0            0           11m

NAME                                              DESIRED   CURRENT   READY   AGE
replicaset.apps/artifactory-ha-nginx-59dc69b597   1         0         0       11m

NAME                                                     READY   AGE
statefulset.apps/artifactory-ha-postgresql               0/1     11m
statefulset.apps/artifactory-ha-artifactory-ha-primary   0/3     11m

However, we're missing the pods!