-
Notifications
You must be signed in to change notification settings - Fork 107
feat(conformance) add EPP unavailable fail-open test #999
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
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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. |
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 @zetxqx! A few small comments, otherwise LGTM.
type: PathPrefix | ||
value: /primary-gateway-test | ||
--- | ||
# --- Conformance EPP service Definition --- |
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.
Would really like to see everything below this in base manifests + reused to simplify test cases.
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.
rebased on #982, and reuse as much as possible. PTAL
# --- InferenceModel Definition --- | ||
# Service for the infra-backend-deployment. | ||
apiVersion: inference.networking.x-k8s.io/v1alpha2 | ||
kind: InferenceModel | ||
metadata: | ||
name: conformance-fake-model-server | ||
namespace: gateway-conformance-app-backend | ||
spec: | ||
modelName: conformance-fake-model | ||
criticality: Critical # Mark it as critical to bypass the saturation check since the model server is fake and don't have such metrics. | ||
poolRef: | ||
name: normal-gateway-pool |
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.
Recommend removing - follow up issue is fine since I know it requires corresponding EPP changes
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.
got it, we can follow up in #1002, also added TODO
Headers: map[string]string{eppSelectionHeaderName: targetPodIP}, | ||
Method: http.MethodPost, | ||
Body: requestBody, | ||
Backend: appPodBackendPrefix, |
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.
In the first test don't we need to ensure that the Gateway routed to a specific Pod, while in the second test any Pod with this prefix is sufficient?
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.
updated, make sure the first request is checking the specific pod and make sure the second request is only checking the prefix.
conformance/utils/traffic/traffic.go
Outdated
|
||
// MakeRequestAndExpectEventuallyConsistentResponse makes a request using the parameters | ||
// from the Request struct and waits for the response to consistently match the expectations. | ||
func MakeRequestAndExpectEventuallyConsistentResponse( |
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.
Please make sure you're converging with @SinaChavoshi on these functions across PRs.
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.
Sure, I'll have a follow up PR to refactor this.
/ok-to-test |
@robscott, I rebased to the main, so it's cleaner ready-to-review now. Re-run the test, results:
|
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 @zetxqx!
/lgtm
/approve Thanks @zetxqx! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danehans, robscott, zetxqx 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 |
…#999) * Add test for epp becoming unavailable and the extensionRef.failureMode is set to failOpen. * resolve minor comments. * format. * import format.
…#999) * Add test for epp becoming unavailable and the extensionRef.failureMode is set to failOpen. * resolve minor comments. * format. * import format.
…#999) * Add test for epp becoming unavailable and the extensionRef.failureMode is set to failOpen. * resolve minor comments. * format. * import format.
This pull request introduces a new conformance test, epp_unavailable_fail_open, to validate the behavior of the extensionRef.failureMode==FailOpen setting.
Verification
gke-l7
istio