-
Notifications
You must be signed in to change notification settings - Fork 135
fix(conformance): Use pinned version of EPP for conformance test instead of main. #1262
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: zetxqx The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @zetxqx. 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. |
@@ -196,7 +196,7 @@ spec: | |||
terminationGracePeriodSeconds: 130 | |||
containers: | |||
- name: epp | |||
image: us-central1-docker.pkg.dev/k8s-staging-images/gateway-api-inference-extension/epp:main | |||
image: us-central1-docker.pkg.dev/k8s-staging-images/gateway-api-inference-extension/epp:v20250725-fb2dfd8 |
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.
Should we use latest release version? The meaning of v20250725-fb2dfd8 is confusing?
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.
I thought about it. Because the current conformance test is using inferencePool v1(https://github.com/kubernetes-sigs/gateway-api-inference-extension/blob/main/conformance/resources/manifests/manifests.yaml#L242) version, however the already released EPP version does not support v1.
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.
That makes sense
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.
is this supposed to be a temporary state until v1 is fully supported?
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.
@nirrozenbaum yes, I would expect that.
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.
is there any time estimation for when is it expected?
I understand that current work on the transition to v1 is still not completed.
having said that, we should keep in mind that pinning the version has a different issue of not getting updates that are merged to main, like bug fixes, etc.
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.
I agree with you on the cons on the pinned image. Use a release version is way better. I'll currently put this PR on hold for further discussion. If some implementers found conformance tests failure, we can ask them to use a pinned version.
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.
@zetxqx since we decided to support both v1 and v1alpha2, do we still need this issue/PR?
or can we close?
/hold |
PR needs rebase. 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. |
Fixes #1258, Used a pinned version of EPP for conformance tests