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

Add node selectors to job and task config #7

Conversation

annymsMthd
Copy link
Contributor

Signed-off-by: Joshua Benjamin joshuabnjmn@gmail.com

@annymsMthd
Copy link
Contributor Author

Looks like the make dockerhub_push should be removed from PRs.

@anandswaminathan
Copy link
Contributor

anandswaminathan commented Jun 3, 2019

@annymsMthd Just merged to master a PR to remove docker_hub push from PRs.

@annymsMthd annymsMthd force-pushed the feature/add-node-selectors-to-job-and-task branch from e6b22f2 to a5e5f36 Compare June 3, 2019 16:15
Copy link
Contributor

@anandswaminathan anandswaminathan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You will also have to run make generate for changes to pkg/apis/app/v1alpha1/types.go to update zz_generated.deepcopy.go

@annymsMthd annymsMthd force-pushed the feature/add-node-selectors-to-job-and-task branch from a5e5f36 to 28b6690 Compare June 3, 2019 21:21
Signed-off-by: Joshua Benjamin <joshuabnjmn@gmail.com>
@annymsMthd annymsMthd force-pushed the feature/add-node-selectors-to-job-and-task branch from 28b6690 to acfda60 Compare June 3, 2019 21:22
@annymsMthd
Copy link
Contributor Author

@anandswaminathan should be gtg now

@mwylde
Copy link
Contributor

mwylde commented Jun 3, 2019

Hey Joshua — can you give a bit more context on why this is needed?

@annymsMthd
Copy link
Contributor Author

Sure thing. In our kubernetes cluster we have different labels for nodes. Since we self host we have dedicated nodes for certain workloads. e.g. ingress, worker, storage, etc.

@annymsMthd
Copy link
Contributor Author

@mwylde @anandswaminathan any reason not to move forward with this? This is a pretty common thing in k8s.

@anandswaminathan anandswaminathan merged commit 1616e73 into lyft:master Jun 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants