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

Introduce ResolvedRefs Status Condition #190

Closed
Tracked by #362
danehans opened this issue Jan 13, 2025 · 4 comments · Fixed by #446
Closed
Tracked by #362

Introduce ResolvedRefs Status Condition #190

danehans opened this issue Jan 13, 2025 · 4 comments · Fixed by #446
Assignees

Comments

@danehans
Copy link
Contributor

danehans commented Jan 13, 2025

Currently, the status subresource for the APIs is undefined. The APIs include several reference type fields, where the existence of these objects are required to implement the intent of the APIs. Similar to Gateway API resources, implementations should verify that the referenced object exists and surface a relevant status condition.

@kfswain
Copy link
Collaborator

kfswain commented Feb 19, 2025

We have status' now in the API, is there still some scope remaining to this issue?

@robscott
Copy link
Member

I think this should be part of our v0.2 release. We should copy or reference the ResolvedRefs condition from Gateway API along with all the associated reasons.

@ahg-g
Copy link
Contributor

ahg-g commented Mar 3, 2025

@danehans are you able to address this?

@ahg-g
Copy link
Contributor

ahg-g commented Mar 3, 2025

/assign @robscott

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants