Closed quadrinho closed 2 months ago
@quadrinho: This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
/remove-kind bug
The recommended configuration is to use NLB https://kubernetes.github.io/ingress-nginx/deploy/#aws
@quadrinho have you tried to configure your target group directly to change the health check target?
By default ingress-nginx seem to use /healtz
as the default health path on port 10254. You should configure your target group to use that.
We are unable to support ALB as its Layer7
/close
@longwuyuan: Closing this issue.
What happened:
Hello,
we try to add with ingress-nginx the object Target Group Binding (from AWS Load Balancer Controller) to use an existing Application Load Balancer Controller.
This is the Target Group Binding used:
The problem is that the health check in the target group is done using http call to "/" and nginx returns 404
What you expected to happen:
Is it possible to configure some values in the nginx chart to not reply 404 to the Balancer?
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.): Chart version 4.2.3
Kubernetes version (use
kubectl version
): 1.23Environment: