Repository navigation
Support orphaned resources cleanup for RunPod - #4404
Merged
Merged
Conversation
This file contains hidden or 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
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.
Follow-up to #4401 for #3453, which implemented orphan cleanup only for AWS.
provider_ref, and pods are listed via the cursor-paginated v2GET /pods, which excludes cluster pods asrun_jobs()is not covered yet.parse_datetime()toutils/common.py, parsing like the API via pydantic, and use it inparse_since(), the Fluent Bit logs storage, and the CLI presets output, which fixes--sincewith aZtimestamp and Fluent Bit timestamps with nanoseconds on Python 3.10.DSTACK_SERVER_ORPHAN_CLEANUP_ENROLLMENT_INTERVAL_SECONDSsetting to speed up enrollment in e2e tests.