-
Notifications
You must be signed in to change notification settings - Fork 72
feat: Initial setup for conformance test suite #720
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
Conversation
Welcome @SinaChavoshi! |
Hi @SinaChavoshi. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This effort is part of #500 |
Thanks @SinaChavoshi! /ok-to-test |
/retest |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @SinaChavoshi! This is a great start!
…version to use semver.
…nce (gateway, epp, model server).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @SinaChavoshi! This mostly LGTM, just a few tiny nits.
…r case, remove unused manifest, remove NamespaceLabels and NamespaceAnnotations
// In future iterations, we will add constants and ConformanceProfile structs for | ||
// EPPProfileName ("EPP") and ModelServerProfileName ("ModelServer") | ||
// to cover their respective conformance layers. | ||
var GatewayLayerProfile = confsuite.ConformanceProfile{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The term "layer" leads me to believe conformance dependencies exist between EPP, Gateway, etc. @robscott does Gateway API have a naming standard for different profiles? IMO, using "component" indicates independence among the profiles.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danehans, SinaChavoshi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
Adding the basic directory structure, core suite files, base manifests, and a placeholder test for InferencePool acceptance, leveraging upstream gateway-api utilities.
This is per design discussed in Conformance Test Technical Design for Gateway API Inference Extension