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.

Sign up for GitHub

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

Jump to bottom

custom node-selector for csiDeployment117/csiDeployment120 #651

Closed
phhutter opened this issue Sep 29, 2021 · 1 comment
Closed

custom node-selector for csiDeployment117/csiDeployment120 #651

phhutter opened this issue Sep 29, 2021 · 1 comment
Labels
tracked

Comments

@phhutter
Copy link

Often you would like to bind infrastructure/core related workload (csiDeployment120YAMLTemplate and csiDeployment117YAMLTemplate) on specific nodes. Therefore it could be useful to have an ability to add node-selectors.
A configuration via helm values.yaml would be preferred.

trident/cli/k8s_client/yaml_factory.go

Lines 666 to 668 in 16e84e6

nodeSelector:
kubernetes.io/os: linux
kubernetes.io/arch: amd64

@gnarl gnarl added the tracked label Oct 4, 2021
@gnarl
Copy link
Contributor

gnarl commented Jan 20, 2022

This issue is resolved with commits e167c7 and c7c167d . This change will be included with the Trident 22.01 release.

@gnarl gnarl closed this as completed Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
tracked
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gnarl @phhutter