BGD-6179 Handle orphaned drivers #253
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HafdisE
force-pushed
the
BGD-6179-handle-orphaned-driver-pods
branch
3 times, most recently
from
009ecac to
7b35b2a
Compare
HafdisE
force-pushed
the
BGD-6179-handle-orphaned-driver-pods
branch
from
7b35b2a to
2f2d5ee
Compare
alextarasov-spot
approved these changes
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira ticket
https://spotinst.atlassian.net/browse/BGD-6179
Description
Introduces the new env vars required to enable the new cleanup mechanisms for orphaned drivers and stuck failed spark app CRs, as well as bumps the image tag to use the new version.
Demo
Checklist
How to test
Apply the chart but set the image.tag to
BGD-6179-handle-orphaned-driver-podsand the image.registry to the private registry.Test plan and results
See PR in the watcher for more details.