-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 test/framework: ensure ApplyClusterTemplateAndWait always returns a cluster #8142
🌱 test/framework: ensure ApplyClusterTemplateAndWait always returns a cluster #8142
Conversation
Cluster Signed-off-by: Stefan Büringer [email protected]
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.
/lgtm
/approve
LGTM label has been added. Git tree hash: 6d662116231b7ecbeb3467d63eeb779b503fb975
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
@sbueringer: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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/test-infra repository. I understand the commands that are listed here. |
/restart known flake will be fixed elsewhere |
Signed-off-by: Stefan Büringer [email protected]
What this PR does / why we need it:
This PR ensures ApplyClusterTemplateAndWait always returns a cluster. This is very useful if a test fails early and we need a cluster to dump and cleanup resources via dumpSpecResourcesAndCleanup.
Let's assume
input.ClusterProxy.Apply(ctx, workloadClusterTemplate, input.Args...)
fails because e.g. the Cluster cannot be deployed because of some issues with the ClusterClass. Then the cluster would be nil and dumpSpecResourcesAndCleanup would panic. This change ensures we always return a cluster so we can get resources from the test run, even if the cluster creation didn't actually work.The same applies when e.g. DiscoveryAndWaitForCluster fails.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #