adding nodeSelector and tolerations to nats helm-chart#1125
Open
ArtPiece55 wants to merge 1 commit intonats-io:mainfrom
Open
adding nodeSelector and tolerations to nats helm-chart#1125ArtPiece55 wants to merge 1 commit intonats-io:mainfrom
ArtPiece55 wants to merge 1 commit intonats-io:mainfrom
Conversation
metacoma
added a commit
to metacoma/shitcluster
that referenced
this pull request
Feb 15, 2026
Nats helm chart doesn't support nodeSelector PR in WIP: nats-io/k8s#1125
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What motivated this proposal?
I would like to deploy NATS on AWS Graviton (arm64) node pools. Both the NATS and prometheus-nats-exporter images provide multi‑arch support (amd64 and arm64), so the chart is already compatible with this architecture.
What is the proposed change?
Add nodeSelector and tolerations configuration to the NATS Helm chart templates and values.yaml, so users can explicitly target particular node pools and architectures for the NATS and exporter pods.
Who benefits from this change?
Users running heterogeneous clusters (for example, mixed amd64 and arm64 pools) can more easily schedule NATS onto cost‑efficient node pools such as AWS Graviton, without having to maintain custom chart forks or extensive overrides.