Adding support to specify SchedularName (optional) in Initializer/Starter/Runner/Stopper Specs/Jobs#783
Open
The-Flash-Routine wants to merge 1 commit intografana:mainfrom
Open
Conversation
…rter/Runner/Stopper Specs/Jobs
Contributor
Author
|
Hi @yorugac |
Contributor
Author
|
Hi @yorugac |
Collaborator
|
Hi @The-Flash-Routine, sorry for the delay, this week is pretty overwhelming! I'll be able to look at this next week. (CI unlocked) |
Contributor
Author
|
Thanks @yorugac :) |
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.
Issue:
#627
PR Changes:
Thoughts:
I understand that using a custom scheduler is a niche use-case, but we should still support all specifications of a Kubernetes Pod when we create a Job
Additional:
I've also raised this improvement issue (easy change)
#784