Add nodeSelector, tolerations and affinity configuration on the component level#332
Conversation
| # my-label: "value" | ||
| podAnnotations: {} | ||
| # my-annotation: "value" | ||
| nodeSelector: {} |
There was a problem hiding this comment.
while you're on it, can you please sort the YAML keys alphabetically?
There was a problem hiding this comment.
Only the ones I added? I reused the same order as it was for common ones.
There was a problem hiding this comment.
Would be nice for all of them :)
|
This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Can you please rebase the pr and put your changes in the right order? |
… level Signed-off-by: Goran Jumic <goran.jumic@optiva.com>
gjumic-optiva
force-pushed
the
component_level_config
branch
from
73c06a5 to
6c8eddd
Compare
Should be done |
As far as I can see it's still not sorted in the values and the resource yaml files? |
|
Please fix merge conflicts. |
2 participants
What this PR does / why we need it
Let's say we have use case:
With current release you are unable to set the podAntiAffinity rules to have 1x nginx and 1x railsserver on Node 1, and other 2 pods one Node 2
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]