I have installed argocd on my eks on AWS playground and nginx ingress as well. However when I try to access the argocd service using the LB A record ( which ends with “us-east-1.elb.amazonaws.com” ) I am unable to do so. Why is that and what do I need to do differently?
It sounds like your ArgoCD service might not be exposed correctly through the LoadBalancer. A few things to double-check, make sure your ArgoCD server service type is set to LoadBalancer if you want direct access, or if you’re using ingress, verify that your ingress controller (like NGINX) is configured with the right annotations for AWS.
Also confirm that your security group for the Load Balancer allows inbound access on the port ArgoCD is using (usually 80 or 443). Sometimes the Load Balancer A record resolves fine, but the connection is blocked by security rules or missing target registration in the target group.
If you’re using the NGINX ingress, try accessing ArgoCD via the ingress hostname instead of the raw LB DNS. Running kubectl get ingress -n argocd should show the hostname you can use.
Once you share a bit more about your service or ingress configuration (YAML snippets), it’ll be easier to spot what’s off.
You should first verify that ArgoCD is installed successfully, either by using a NodePort or by forwarding the port to access the UI.
To access the Kubernetes cluster through the ALB, you may need to configure a Kubernetes Ingress and set up the ALB listener properly with a DNS name and target rules.
The information you’ve provided isn’t enough to assist you further. Could you please share more details about your setup?