feat: suspend cronjobs when services are idled#55
Draft
shreddedbacon wants to merge 1 commit into
Draft
Conversation
shreddedbacon
force-pushed
the
disable-cronjobs
branch
from
95dc7be to
025f5a7
Compare
shreddedbacon
force-pushed
the
disable-cronjobs
branch
2 times, most recently
from
9b29bc8 to
46b99ac
Compare
shreddedbacon
force-pushed
the
disable-cronjobs
branch
from
46b99ac to
9fdfa3b
Compare
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
2 participants
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.
When environments are idled, kubernetes cronjob definitions remain active. This can lead to pods starting and crashing due to resources that may not be available.
This PR aims to introduce a mechanism to mark kubernetes cronjobs as disabled when an environment is idled. When the environment is unidled, the cronjobs get enabled again.
closes #54