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

helm: add option to split load by node affinity #347

Merged
merged 1 commit into from
Jul 24, 2020

Conversation

diegodelemos
Copy link
Member

No description provided.

@diegodelemos diegodelemos marked this pull request as ready for review July 20, 2020 14:40
helm/reana/README.md Outdated Show resolved Hide resolved
helm/reana/templates/reana-cache.yaml Outdated Show resolved Hide resolved
helm/reana/templates/reana-workflow-controller.yaml Outdated Show resolved Hide resolved
helm/reana/templates/roles.yaml Outdated Show resolved Hide resolved
@diegodelemos diegodelemos force-pushed the node-affinity branch 2 times, most recently from 8f8d980 to a6e4f55 Compare July 21, 2020 09:15
helm/reana/README.md Outdated Show resolved Hide resolved
helm/reana/README.md Outdated Show resolved Hide resolved
Copy link
Member

@tiborsimko tiborsimko left a comment

Choose a reason for hiding this comment

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

All scenarios work nicely.

helm/reana/README.md Outdated Show resolved Hide resolved
* Uses explicit nodeSelector on infrastructure pods since the pods will
  be deployed to a namespace selected by the user (through
  `helm install --namespace foo`) or to the default namespace.
  Therefore we cannot modify the user namespace and specify a nodeSelector
  at namespace level. For runtime pods, since we create the namespace, we
  can specify a nodeSelector for the whole namespace.
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