-
Notifications
You must be signed in to change notification settings - Fork 204
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
Healthz issue with HAProxy Kubernetes Ingress Controller and Hashicorp Consul Connect (service mesh) #686
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
News on this ?! HAProxy cannot be used with consul connect (mesh). |
Hi, we need to know if is possible use consul with haproxy too. any news? |
I experienced the same issue, after 1 week of analysis and attempts I was unable to find a solution. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi, |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi, |
Not sure if this is related to haproxy kubernetes ingress controller helm chart or the inress controller itself.
I also opened an issue in the haschicorp consul issue tracker
hashicorp/consul#21993
Can you help me on this issue ? I want to use HAProxy as ingress to control nord-sud kubernetes traffic but until this issue is active I cannot use HAProxy Ingress controller and we need to opt to use Hashicorp API Gateway.
You can se in the issue referenced to link above that enabling consul connect injector with sidecar proxy in trasparent proxy mode, haproxy cannot start, not passing health checks (1043/healthz). And disabling transparent proxy mode HAProxy cannot access other services inside the service mesh (services under consul connect, ACLs, Intentions, etc.).
The text was updated successfully, but these errors were encountered: