Closed twintag-ciprian-pista closed 1 month ago
It's a bit difficult to see what issue you are running into. Can you provide more information as to what error messages you are getting and what you've tried?
Hello,
I am trying to access the LB of the ARGO cd to login in the Interface of ARGO: k8s-argocd-argocdar-b58ba5914a-1e2b2273bd87b3f1.elb.eu-central-1.amazonaws.com
This link is returning a timeout response. I already forwarded the port locally and ARGOCD is working fine, I was able to access it, I checked the RT IGW NATGW everything looks ok.
I do not know I am missing in order to access the ARGOCD UI.
Thanks Ciprian
On Thu, Dec 7, 2023 at 8:21 PM Manabu McCloskey @.***> wrote:
It's a bit difficult to see what issue you are running into. Can you provide more information as to what error messages you are getting and what you've tried?
— Reply to this email directly, view it on GitHub https://github.com/awslabs/crossplane-on-eks/issues/157#issuecomment-1845883938, or unsubscribe https://github.com/notifications/unsubscribe-auth/BED5BHZAHVVBJKO43VZOWQLYIICLVAVCNFSM6AAAAABAJG7YD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBVHA4DGOJTHA . You are receiving this because you authored the thread.Message ID: @.***>
Were you able to get access to the Prometheus & Grafana LB endpoints? If you run a kubectl get service -n kube-prometheus-stack
you can get the other LB's.
Fixed by adding an annotation to the Load Balancers.
ARGO CD is not available to access it from DNS URL
Provide link to the example related to the quesiton
k8s-argocd-argocdar-b58ba5914a-1e2b2273bd87b3f1.elb.eu-central-1.amazonaws.com
Can anyone help?