-
Notifications
You must be signed in to change notification settings - Fork 92
Gimbal doesn't remove OpenStack endpoint from service with health check setting #208
Comments
Thank you @yutaokaz. Do you recall what reconciliation period was configured in the OpenStack discoverer? Did the OpenStack discoverer run a reconciliation after you deleted the LBaaS member? My initial thinking around this issue is that the Endpoints object in the Gimbal cluster still had the IP addresses of the OpenStack VMs. Given that you did not destroy the VMs, but instead removed them from the load balancer, the VMs are still reachable for traffic. We should expect the removed endpoint to stop responding if either a) the OpenStack discoverer reconciles the OpenStack state with the gimbal state, or b) the VM itself is destroyed, triggering the health check to fail. |
Hi @alexbrand, thank you for your reply. |
Thanks for the additional information @yutaokaz. I will try to reproduce this on our side. |
@yutaokaz This seems to be an issue with Envoy, so I have opened projectcontour/contour#603. |
Contour will fix this in 0.7.0, moving to Gimbal 0.4.0 milestone. |
Punted to Contour 0.9 |
What steps did you take and what happened:
neutron lbaas-member-delete
command.What did you expect to happen:
I expect to get response from 1 (remained) endpoint.
Environment:
OpenStack. In terms of Kubernetes, I haven't checked.
https://github.com/heptio/gimbal/tree/release-0.3.0-beta.2
gcr.io/heptio-images/contour:v0.6.0-beta.2
gcr.io/heptio-images/gimbal-discoverer:v0.3.0-beta.2
The text was updated successfully, but these errors were encountered: