-
Notifications
You must be signed in to change notification settings - Fork 681
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]Blanket Tolerations / Affinity for all node executions #439
Comments
kumare3
added
enhancement
New feature or request
untriaged
This issues has not yet been looked at by the Maintainers
labels
Jul 31, 2020
cc @jeevb |
kumare3
removed
the
untriaged
This issues has not yet been looked at by the Maintainers
label
Jul 31, 2020
This was referenced Jul 31, 2020
Closed
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 6, 2022
* updated ExecutionNotFound to check failed attempts rather than workflow state Signed-off-by: Daniel Rammer <[email protected]> * added unit test to allow continue until maxRetries Signed-off-by: Daniel Rammer <[email protected]> * added dropping ExecutionNotFound error when aborting workflow Signed-off-by: Daniel Rammer <[email protected]> * fixed unit tests Signed-off-by: Daniel Rammer <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 6, 2022
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 20, 2022
* Added snowflake example Signed-off-by: Kevin Su <[email protected]> * Updated rst files Signed-off-by: Kevin Su <[email protected]> * Updated rst files Signed-off-by: Kevin Su <[email protected]> * Updated rst files Signed-off-by: Kevin Su <[email protected]> * Rebased PR Signed-off-by: Kevin Su <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Aug 9, 2023
* updated ExecutionNotFound to check failed attempts rather than workflow state Signed-off-by: Daniel Rammer <[email protected]> * added unit test to allow continue until maxRetries Signed-off-by: Daniel Rammer <[email protected]> * added dropping ExecutionNotFound error when aborting workflow Signed-off-by: Daniel Rammer <[email protected]> * fixed unit tests Signed-off-by: Daniel Rammer <[email protected]>
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Aug 21, 2023
eapolinario
pushed a commit
that referenced
this issue
Sep 26, 2023
* init Signed-off-by: byhsu <[email protected]> * fix typo Signed-off-by: byhsu <[email protected]> --------- Signed-off-by: byhsu <[email protected]> Co-authored-by: byhsu <[email protected]>
pvditt
pushed a commit
that referenced
this issue
Dec 29, 2023
* init Signed-off-by: byhsu <[email protected]> * fix typo Signed-off-by: byhsu <[email protected]> --------- Signed-off-by: byhsu <[email protected]> Co-authored-by: byhsu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation: Why do you think this is important?
In cases when Flyte is deployed to a shared environment (shared with online services etc), users may want to segregate all pods scheduled by Flyte to a separate node pool. This can be achieved using affinity or tolerations. This change will make it easy to apply such affinity / tolerations to all K8s executions - Containers (python task etc), sidecars, pytorch etc (even spark after spark 3.0)
Goal: What should the final outcome look like, ideally?
All pods scheduled land on some specific node pool configured in the backend.
Describe alternatives you've considered
use sidecar for every execution, this prevents using other task types easily
Flyte component
[Optional] Propose: Link/Inline
NA
Additional context
This will help solve Issue #435 Part - 1
Is this a blocker for you to adopt Flyte
NA
The text was updated successfully, but these errors were encountered: