Skip to content
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

Team based Kubernetes Node Selectors #89

Open
tlawrie opened this issue Apr 7, 2021 · 0 comments
Open

Team based Kubernetes Node Selectors #89

tlawrie opened this issue Apr 7, 2021 · 0 comments
Labels
enhancement New feature or request project: flow Tasks for Boomerang Flow

Comments

@tlawrie
Copy link
Member

tlawrie commented Apr 7, 2021

Is your request related to a problem? Please describe.
Currently the only way to define where a task runs is the node selector at install time for all tasks across the instance

Describe the solution you'd like
Allow individual teams to have their own node selectors

Describe the benefits or justification for this request
Allows greater segregation and control of running tasks

Specific workflows could be GPU or client specific at the infra layer. Allowing a broader use case of the as a service and user needs for different types of workflows.

Additional context
Add any other context or screenshots about the feature request here.

@tlawrie tlawrie added the enhancement New feature or request label Apr 7, 2021
@tlawrie tlawrie added the project: flow Tasks for Boomerang Flow label Jun 9, 2021
@tlawrie tlawrie changed the title Kubernetes Node Selectors Team based Kubernetes Node Selectors Sep 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request project: flow Tasks for Boomerang Flow
Projects
Status: No status
Development

No branches or pull requests

1 participant