feat: override to be able to force cronjob into service pod #349
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.
In some cases, a cronjob that would typically be run as a native kuberentes
CronJob
type may be better to run within the pod of the service directly. Since the in pod and native kubernetes switch is based on the interval of the cronjob, there is no way to do this without increasing the frequency of the cronjob, or writing a wrapper around the cronjob.This offers a simple way to tell a cronjob to run in the service pod instead of a kubernetes native
CronJob
by way of aninPod
field.Set this to
true
, and the pod will be converted to an in pod cronjob: