[feature-request] helm-nats: add nodeSelector and tolerations

[ArtPiece55]

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.

What alternatives have you evaluated?

[wallyqs]

do you want to send PR?

[ArtPiece55]

i can prepare it, once have some free time

[ArtPiece55]

created the pull-request

[metacoma]

Hello, any updates here?

My Kubernetes cluster configuration looks like this:

$ kubectl get nodes
NAME    STATUS   ROLES           AGE   VERSION
mcmp2   Ready    control-plane   75d   v1.34.1
mcmp3   Ready    control-plane   75d   v1.34.1
mcmp4   Ready    worker          75d   v1.34.1
mcmp5   Ready    worker          75d   v1.34.1
mcmp6   Ready    worker          75d   v1.34.1
mcmp7   Ready    worker          75d   v1.34.1
mcmp8   Ready    worker          75d   v1.34.1
mcmp9   Ready    control-plane   75d   v1.34.1

I would like to have the ability to deploy NATS only on worker nodes.

[metacoma]

@ArtPiece55 #810 (comment)

Have you tried this approach?