-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS alb + Ingress + k8s 1.22 #8067
Comments
Same issue with k8s 1.21 AWS alb ingress error: error validating "argocdingresstrafic.yml": error validating data: [Valid.IngressBackend, ValidationError(Ingress.spec.rules[0].http.paths[0].backend): up.paths[1].backend): unknown field "serviceName" in io.k8s.api.networking.v1.Ing.api.networking.v1.IngressBackend]; if you choose to ignore these errors, turn validation off with --validate=false |
This issue can be fixed by reformatting your ingress service spec to: `spec:
|
I'm having this same issue, even after updating the spec to match the new format:
The ingress is created sucessfully but no alb loadbalancer or controller is created and the ingress has no address (should be the address of the alb loabalancer) Here is my service:
|
Hello, I am also seeing issues when I follow the docs. I can only get my ingress to fully deploy AND serve traffic (i.e register the argo-server pod) to successfully register the pod to the two target groups only when I set:
What aws load balancer controller version are you running? I had to rewrite ALL my ingress files very recently when I moved from 2.1.3 to 2.4.0. The big gotcha for me is that the following is now deprecated and should be replaced with this:
However it is good for everyone to know it's now deprecated` in favour for the below!
|
In case anyone else is coming here with the same problem, the solutions for me was to patch the argocd-server to use updated files for reference: overlays/argocd-server.yaml
base/argogrpc.yaml
ingress-class.yaml
ingress.yaml
kustomize.yaml
base/argocd.yaml is just the basic application
|
Hey Guys, I'm wondering if any of you were able to use the security group with ALB?
The security group is allowing TCP on 443, but after adding the security group to ALB I'm getting 504 status code. Sorry if my question don't fit this topic. |
Hi, I've never used security-groups. I've always just allowed the controller to dynamically create (and destory) the SGs using the https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/guide/ingress/annotations/#inbound-cidrs annotation. I don't use this for my Argo Ingress but do use the inbound-cidrs annotation for 99% all of my other Ingress services. |
I used AWS Application Load Balancers and the argogrpc targetGroup is unhealthy and the UI returns 502 |
I was encountering this issue, and this helped. |
@arbianqx My argogrpc target group is unhealthy, what is the Health check path of your argogrpc target group ? |
Hey guys, for everyone with this problem, the issue comes from the default argocd service, which is a ClusterIP, when the AWS load balancer controller needs a Nodeport to deploy an ALB. Patching or deploying the service as NodePort will make it work. |
@vumdao Set |
Describe the bug
I tried to follow the "AWS Application Load Balancers (ALBs) And Classic ELB (HTTP Mode)" tutorial, it is not compatible with k8s 1.22. I've changed the configuration and it is still note working.
To Reproduce
I used the latest stable argo-cd.
Service:
Ingress:
Expected behavior
I don't see any load balancer created.
Screenshots
If applicable, add screenshots to help explain your problem.
Version
Paste the output from `argocd version` here.
Logs
The text was updated successfully, but these errors were encountered: