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

Fix HTTPRoute section name related bugs #568

Merged
merged 3 commits into from
Apr 13, 2023
Merged

Conversation

pleshakov
Copy link
Contributor

- Previously, NKG assumed section names in parentRefs of HTTPRoute
were unique, even when they referenced different Gateways. This
commit fixes that. Fixes #484
- Previously, when NKG reported status for a parentRef with an empty
section name, it would give the ref the name "unattached" in
the HTTPRoute status. This behavior is not Gateway API spec compliant --
the API prescribe to use empty section name in that case. Now NKG
will use empty section name. See the corresponding
FIXME in the code https://github.com/nginxinc/nginx-kubernetes-gateway/blob/b594695bb42a79653eb8217a6dfd00c6d9594d5b/internal/state/statuses.go#L151
Note: the FIXME advice is wrong.
- Previously, in case of multiple parentRefs in an HTTPRoute, when
reporting their statuses in the HTTPRoute status, NKG could change
the order of the refs in the status. This commit restores the order.
See the corresponding FIXME in
the code https://github.com/nginxinc/nginx-kubernetes-gateway/blob/b594695bb42a79653eb8217a6dfd00c6d9594d5b/internal/status/httproute.go#L25
@pleshakov pleshakov requested a review from a team as a code owner April 10, 2023 21:34
@github-actions github-actions bot added the bug Something isn't working label Apr 10, 2023
@pleshakov pleshakov merged commit 918d650 into main Apr 13, 2023
12 checks passed
@pleshakov pleshakov deleted the fix/sectionnames-cols branch April 13, 2023 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

SectionNames should not collide
2 participants