Skip to content

AIGatewayRoute should use parentRefs, not targetRefs #550

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

Open
arkodg opened this issue Apr 2, 2025 · 2 comments · May be fixed by #580
Open

AIGatewayRoute should use parentRefs, not targetRefs #550

arkodg opened this issue Apr 2, 2025 · 2 comments · May be fixed by #580
Assignees
Labels
api Control Plane API enhancement New feature or request
Milestone

Comments

@arkodg
Copy link

arkodg commented Apr 2, 2025

Description:

Describe the issue.

The idiomatic way for https://aigateway.envoyproxy.io/docs/api/#aigatewayroutespec to link to a Gateway is using a parentRefs field, not a targetRefs field
https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.ParentRef

[optional Relevant Links:]

Any extra documentation required to understand the issue.

@mathetake
Copy link
Member

makes sense! we can deprecate TargetRefs and introduce ParentRefs

@mathetake mathetake added enhancement New feature or request api Control Plane API labels Apr 14, 2025
@mathetake mathetake added this to the v0.2.0 milestone Apr 17, 2025
@mathetake
Copy link
Member

this should be done before v0.2.0

@mathetake mathetake self-assigned this Apr 17, 2025
@mathetake mathetake linked a pull request Apr 18, 2025 that will close this issue
@mathetake mathetake modified the milestones: v0.2.0, v0.3.0 May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Control Plane API enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants