-
Notifications
You must be signed in to change notification settings - Fork 206
Improvements to the E2E Test utilities #1853
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
Signed-off-by: Shmuel Kallner <[email protected]>
Signed-off-by: Shmuel Kallner <[email protected]>
|
@shmuelk: The label(s) In response to this:
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 project configuration. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nirrozenbaum, shmuelk 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 |
* Enable specifying a K8S context for the E2E tests Signed-off-by: Shmuel Kallner <[email protected]> * Return kind/name for created objects Signed-off-by: Shmuel Kallner <[email protected]> --------- Signed-off-by: Shmuel Kallner <[email protected]>
What type of PR is this?
/kind test
What this PR does / why we need it:
This PR enables the passing of a Kubernetes context into the End to End test utilities.
The llm-d-inference-scheduler will use to enable running End to end tests on pre-existing clusters. There are requests for this capability downstream from the llm-d-inference-scheduler.
In addition a minor change was made to return the kind and name of created objects. This is needed in the llm-d-inference-scheduler to enable it to cleanup after End to end tests run on pre-existing clusters.
Does this PR introduce a user-facing change?:
NONE