nats-server | Performance server for NATS.io , the cloud and edge native | Messaging library

I am currently creating a helm chart for my fullstack application, and I would like to install a nats helm chart to it as a dependency. I know I can add it as a dependency in the Charts.yml file, but how can I provide the nats chart with a Values.yml to overrride the default nats chart values? What I would like is that when I do a helm install for my application, it also installs the nats dependency but with custom values.yml.

chart.yml dependency section

Essentially what the subject says. I was wondering if there are there benefits to be gained performance-wise by using the same encryption/decryption mechanism when clients communicate via messages sent-to/received-from the same nats server.

I have posed the same question here if anyone is interested:

https://github.com/nats-io/nats-server/discussions/2740

Consider for instance the following two scenarios for nats-based communication:

• Scenario#1:

A publisher (P) is publishing over to nats on subject "foo.bar", using encryption-decryption-scheme (A) with his own encryption-key (A)

A consumer (C) is subscribed to nats-subject "foo.bar", using encryption-decryption-scheme (B) with his own encryption-key (B)

In this scenario I assume that that nats-server will decrypt messages published by (P) using decryption scheme (A) examine the subject and forward "foo.bar" messages over to consumer (C) after having re-encrypted these messages using encryption-scheme (B).

• Scenario#2:

A publisher (P) is publishing over to nats on subject "foo.bar", using encryption-decryption-scheme (A) with his own encryption-key (A)

A consumer (C) is subscribed to nats-subject "foo.bar", using the exact same encryption-decryption-scheme (A) as the publisher

In this scenario I assume that that nats-server would only need to decrypt just the subject of the message published by (P) using decryption scheme (A) and after examining the subject it would forward "foo.bar" messages over to consumer (C) by "copy-pasting" the payload (data) of the message "as-is" since the encryption-decryption mechanism is the exact same.

I guess this symmetry in encryption-decryption should provide better performance when the load is high.

Am I right in these assumptions? Or do I miss something? I haven't seen anyone pointing out scenario#2 as a means to boost performance and reduce latency (potentially reducing error rates as well).

Thoughts? Insights? Links to relevant documentation?

I'm doing my first steps with NATS and see behavior I cannot make sense of, even after reading the docs quite carefully. I have a local NATS server (2.6.5) running. It was started with

One of the pods in my local cluster can't be started because I get Unable to attach or mount volumes: unmounted volumes=[nats-data-volume], unattached volumes=[nats-data-volume nats-initdb-volume kube-api-access-5b5cz]: timed out waiting for the condition error.

When I try to create a stream on the local NATS server get the error. The connection established successfully but on jsm.addStream(conf) request broke.

I'm using maven artifact:

I wanted to test a very basic application for NATS-streaming on Kubernetes. To do so, I followed the commands from the official NATS-docs.

It basically comes down to running

My problem is that I need to increase max_payload value that NATS receive but I have no idea where I can do it.

The project is using Moleculer and NATS is created as a container with docker.

When I try to make a request which is bigger than 1MB NATS returns:

I am currently building an application using NestJS by following microservice architecture. And use NATS as a messaging system. It works fine on my local machine but I am unable to dockerized the NATS server.

The folder structure of my project: