Forum Discussion
Altocumulusmonitor/healthcheck issue with envoy gateway
Hello everyone
I’m experiencing an issue with one of our implementations. The server team has deployed an Envoy Gateway using a MetalLB IP (Kubernetes environment).
We have three VIPs: 10001, 10002, and 443. All of them are configured as passthrough, with no special settings or iRules. From what I understand, the pool member is a MetalLB IP that forwards traffic to three backend nodes.
I configured standard TCP health monitors (basic 3-way handshake), but for some reason, the pool member is marked as down. I’ve done extensive troubleshooting (including tcpdump captures), and I can confirm that the 3-way handshake completes successfully. However, immediately after that, the load balancer sends a TCP reset.
This suggests that communication works in both directions, so the network itself seems fine.
I also tried creating a custom TCP monitor using alias address and port (based on the three nodes provided), but the monitor still fails. Interestingly, when I configure those three servers directly as pool members, the pool status is up.
Has anyone encountered a similar issue or have any ideas on what else I could check?
2 Replies
lost1rulost2Nimbostratus
Do you have a config snippet you can share?
- Melissa_C
Moderator
Hello miodas
I noticed there was a response for possibility of additional details being needed to assist, if you are still needing assistance I'd like to encourage you to provide details. However, if you have got a resolution if you could please provide an update and mark your post as solved for yourself and other users who may run into this in the future.
-Melissa
