-
Notifications
You must be signed in to change notification settings - Fork 14
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
e2e: must-gather: fix the setup process #1120
Conversation
make sure we always have a scheduler object reference if both we setup it explicitly or if we skip the setup and just check what the cluster have. Signed-off-by: Francesco Romani <[email protected]>
carrying forward #1115 because holidays |
/cc @Tal-or |
make sure the context and timeouts are properly passed down and honored. Signed-off-by: Francesco Romani <[email protected]>
0f88378
to
82b4e49
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ffromani, Tal-or 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 |
/cherry-pick release-4.18 |
@ffromani: #1120 failed to apply on top of branch "release-4.18":
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. |
In case we are skipping the setup, make sure to fetch the existing scheduler data, failing loudly if that resource is not actually present.
Along the way, cleanup the deploy API and package to make sure context and timeout are properly passed down the call chain.