-
Notifications
You must be signed in to change notification settings - Fork 349
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
HTTPRoute w/ two parent gateways - Both get configured, only one is shown in status, and which switches #4264
Comments
Tried removing the extraneous resources, and it didnt help. egctl status ❯ egctl x status all -v -A
NAME TYPE STATUS REASON MESSAGE OBSERVED GENERATION LAST TRANSITION TIME
gatewayclass/cluster Accepted True Accepted Valid GatewayClass 1 2024-09-14 12:00:45 +0200 CEST
gatewayclass/internal Accepted True Accepted Valid GatewayClass 2 2024-09-14 12:00:45 +0200 CEST
NAMESPACE NAME TYPE STATUS REASON MESSAGE OBSERVED GENERATION LAST TRANSITION TIME
envoy-gateway gateway/cluster Programmed True Programmed Address assigned to the Gateway, 1/1 envoy Deployment replicas available 1 2024-09-17 11:24:37 +0200 CEST
Accepted True Accepted The Gateway has been scheduled by Envoy Gateway 1 2024-09-17 11:24:27 +0200 CEST
envoy-gateway gateway/internal Programmed True Programmed Address assigned to the Gateway, 1/1 envoy Deployment replicas available 1 2024-09-17 11:28:25 +0200 CEST
Accepted True Accepted The Gateway has been scheduled by Envoy Gateway 1 2024-09-17 11:25:23 +0200 CEST
NAMESPACE NAME TYPE STATUS REASON MESSAGE OBSERVED GENERATION LAST TRANSITION TIME
dev-ops httproute/webapi ResolvedRefs True ResolvedRefs Resolved all the Object references for the Route 1 2024-09-17 11:34:22 +0200 CEST
Accepted True Accepted Route is accepted 1 2024-09-17 11:34:22 +0200 CEST
Error: no matches for kind "BackendTLSPolicy" in version "gateway.networking.k8s.io/v1alpha2"
no matches for kind "BackendTLSPolicy" in version "gateway.networking.k8s.io/v1alpha2" |
another bug in the area of parentRef status #4127 |
@zhaohuabing is this fixed ? |
@arkodg Looks like this was caused by the same reason which has been fixed in #4336. @BadLiveware Can you help confirm if this issue still exists in the latest EG? |
@zhaohuabing Still an issue on v1.1.2 or do you mean v0.0.0-latest? |
v0.0.0-latest, thanks. |
@BadLiveware Did you get chance to test it on v0.0.0-latest? |
@zhaohuabing Yes, it still behaves the same, configures both gateways but only sets one in status |
I reproduced this issue in my dev machine. The two Gateways belong to different GatewayClasses, so they were translated separately. As a result, the HTTPRoute parent status were overriden by the later translation. This issue also exists for other Route types. |
thanks for triaging this one @zhaohuabing, to fix this issue, we'll need to not override the entire
Patch rather than a Update
relates to kubernetes-sigs/gateway-api#1629 |
Description:
I have 3 different gateways up and running, only 2 of which are used in this issue.
Only one gateway is shown in status, while both are configured. This results in things like external-dns only setting up DNS records for one gateway address.
Repro steps:
Overview:
Same HTTPRoute switches its status between gateways
(Part) Config dump to show both gateways are actually configured:
internal:
cluster
Environment:
GKE 1.29
Envoy Gateway v1.1.0
Upgraded to envoy gateway v1.1.1 after writing this issue, and it remains an issue
Logs:
downloaded-logs-20240917-102549.csv
The text was updated successfully, but these errors were encountered: