generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Redefined Gateway API Types #115
Comments
cc: @robscott |
Good catch, thanks @danehans! The goal here was to add some defaults here so 99% of users would only need to specify a name, similar to how BackendRef works in Gateway API. Those have been added now, so hopefully it makes a bit more sense: gateway-api-inference-extension/api/v1alpha1/inferencemodel_types.go Lines 71 to 89 in 60bab3a
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, gateway-api-inference-extension defines API types that exist in Gateway API. For example:
Gateway API defines custom alias types for
Group
,Kind
, andName
. For consistency, should these types be imported and used instead of redefining them as opaque strings? For example:The text was updated successfully, but these errors were encountered: