Skip to content
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 parentRef status leftovers after update #5277

Closed
1 of 2 tasks
mlavacca opened this issue Dec 4, 2023 · 0 comments · Fixed by #5477
Closed
1 of 2 tasks

HTTPRoute parentRef status leftovers after update #5277

mlavacca opened this issue Dec 4, 2023 · 0 comments · Fixed by #5477
Assignees
Labels
area/gateway-api Relating to upstream Kubernetes SIG Networking Gateway API bug Something isn't working
Milestone

Comments

@mlavacca
Copy link
Member

mlavacca commented Dec 4, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Problem Statement

When an *Route references a parent through the ParentRef section, a new ParentStatus gets created in the route status, with the whole set of conditions. After an update on the Route's ParentReferences (change the parent from gatewayA to gatewayB), the ParentStatus for GatewayB gets appended to the already existing ParentStatuses instead of replacing them.

Acceptance Criteria

  • the ParentStatus content has a 1:1 relationship to the ParentRef in the route spec.
@mlavacca mlavacca added bug Something isn't working area/gateway-api Relating to upstream Kubernetes SIG Networking Gateway API labels Dec 4, 2023
@mflendrich mflendrich added this to the KIC v3.1.x milestone Dec 4, 2023
@czeslavo czeslavo self-assigned this Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gateway-api Relating to upstream Kubernetes SIG Networking Gateway API bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants