ArgoCD LoadBalancer not provisioning about cloud-native-spring-in-action HOT 4 CLOSED

@jempitman thanks for reporting the issue. Could you share more details about your setup on DigitalOcean so I'll try to reproduce it? What Kubernetes version is the cluster using? (You can check it by running the doctl k8s cluster get polar-cluster command.) Was it created following the steps in the book or does it have any additional configuration?

I tried with both the version used in the book and the latest one, and managed to get an external IP address provisioned within 3/4 minutes. My cluster is running version 1.26.3-do.0.

Thank you!

from cloud-native-spring-in-action.

Thank you for your response, my cluster is also running version 1.26.3-do.0 and was set up without any additional configuration, only using the scripts provided in the PolarBookshop repo.

(edit) Also, I have redeployed my cluster and tried deploying argocd with the version in the deploy.sh and the latest script and have the same issue

from cloud-native-spring-in-action.

After some digging I have found the root cause of the problem: there seems to be a limit on the number of Load Balancers that may be created (a maximum of 2) and after applying all the standardised shell scripts from Appendix B this limit is already reached so an External IP address cannot be provisioned for ArgoCD.

I was able to find the problem by entering the following command (also shown in the attached screenshot):

kubectl describe service argocd-server -n argocd

After deleting one of the automatically created Load Balancers via the Digital Ocean portal in my browser I was able to continue and complete the GitOps deployment with ArgoCD. I suppose this limit is linked to the Terms & Conditions of the evaluation licence, but I have not yet found any additional information about it on the site.

from cloud-native-spring-in-action.

Support for Digital Ocean has confirmed that a maximum of 2 LoadBalancers can be provisioned on an evaluation/ trial license, so it is not possible to deploy the argocd-server without either removing one of the backing services or waiting until the evaluation period is finished and additional billing history is established.

from cloud-native-spring-in-action.