Closed abalestrini closed 1 week ago
I used HTTPS as backend protocol. My target group looks healthy.
kubernetes.io/ingress.class : alb
alb.ingress.kubernetes.io/backend-protocol: HTTPS
alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS":443}]'
alb.ingress.kubernetes.io/scheme: internal
alb.ingress.kubernetes.io/target-type: ip
Hi @timam I think that using the backend-protocol as HTTPS
would conflict with my current config because I set up the server with insecure: true
. I might give it a try though
Thanks @timam for your comment, it worked. Sharing the final configuration
configs:
params:
server.insecure: false
global:
domain: argo.staging.my.domain.com
server:
ingress:
enabled: true
controller: aws
ingressClassName: alb
annotations:
alb.ingress.kubernetes.io/load-balancer-name: 'k8s-staging-argo-cd-alb'
alb.ingress.kubernetes.io/scheme: internal
alb.ingress.kubernetes.io/target-type: ip
alb.ingress.kubernetes.io/subnets: subnet-xxxxxxxxx, subnet-xxxxxxxxx
alb.ingress.kubernetes.io/backend-protocol: HTTPS
alb.ingress.kubernetes.io/healthcheck-protocol: HTTPS
alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS": 443}]'
alb.ingress.kubernetes.io/ssl-redirect: '443'
aws:
serviceType: ClusterIP
backendProtocolVersion: GRPC
Describe the bug
I got argoCD implemented in my EKS cluster and wanted to expose the UI through the ingress that this Helm chart provides by using an AWS ALB. The fact is that while the ingress is created properly I got a
health check
error in the ALB TG. The configuration is the followingHere you can see what the ALB target groups look like
Related helm chart
argo-cd
Helm chart version
6.7.1
To Reproduce
-
Expected behavior
The ingress should be created correctly allowing me to use it to reach the argocd UI.
Screenshots
Additional context
Sharing the ingress manifest as it was created by the chart:
and here is the backend service created by the helm chart too