You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It has the failover-gateway.duckdns.org as a lb_endpoint. However, when I use the same upstream and configure an HTTPRoute and Gateway API to point to the upstream:
Gloo Edge Product
Open Source
Gloo Edge Version
1.18.x
Is your feature request related to a problem? Please describe.
Currently it doesn't look like Upstream Failover is support in the k8 gateway api. It works when it's configured in with the edge apis.
Using Edge API on 1.18.4:
The following cluster is generated:
It has the
failover-gateway.duckdns.org
as a lb_endpoint. However, when I use the same upstream and configure an HTTPRoute and Gateway API to point to the upstream:The envoy config doesn't have the
failover
address in the lb_endpoint:So when you try to ping the endpoint after the upstream host
primary-gateway.duckdns.org:80
is down, it never switchs to the failover endpoint:Describe the solution you'd like
Feature parity with edge api.
Describe alternatives you've considered
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: