-
Notifications
You must be signed in to change notification settings - Fork 28k
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
[SPARK-38241][K8S][TESTS] Close KubernetesClient in K8S integrations tests #35555
Conversation
Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
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.
Thank you, @martin-g .
BTW, Apache Spark community has a convention to use |
Can one of the admins verify this patch? |
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, it reasonable to close the client after suite.
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.
Sorry folks.
This PR has been blocked due to the recent Docker Desktop validation issue.
- f33e371
- bc6eb92
- [SPARK-38272][K8S][TESTS] Use
docker-desktop
instead ofdocker-for-desktop
for Docker K8S IT deployMode and context name #35595 - [SPARK-38244][K8S][BUILD] Upgrade kubernetes-client to 5.12.1 #35596
We've been very careful because of the previous outage.
@dongjoon-hyun Thanks, it reasonable for careful at this stage. @martin-g I also tested it in my k8s, it works as expected, but the |
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.
+1, LGTM. Merged to master.
What changes were proposed in this pull request?
Close org.apache.spark.deploy.k8s.integrationtest.backend.IntegrationTestBackend#getKubernetesClient in the
cleanUp()
of the backend implementations.Why are the changes needed?
It is a good practice to cleanup resources at the end of the tests, so they do not leak and affect other tests.
Recently I've noticed the following in the output:
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Run the IT tests