Closed aDisplayName closed 8 months ago
you need to remove this to be able to use the account CRDs first:
jetstream:
nats:
url: nats://nats-engine-headless:4222
you need to remove this to be able to use the account CRDs first:
jetstream: nats: url: nats://nats-engine-headless:4222
You are right! After removing those lines, it worked!
What version were you using?
nats-server: v2.10.9
What environment was the server running in?
nats:2.10.9-alpine natsio/jetstream-controller:0.14.1
Is this defect reproducible?
The nats server is configured using following helm chart:
with following configuration
The nack is deployed using helm chart:
The configuraiton for nack helm is
Given the capability you are leveraging, describe your expectation?
We still want use the nats server's configuration to manage different account settings and credential. In our example, the plain username / password.
But we want to leverage Nack to manage different jetstream under different accounts. Here is the CRDs we tried to apply:
We are expecting when using
nats stream info
command to check stream status, we will see streamjs-app
when using userapp
to access, and see streamjs-client
when using userclient
to access.And since we are using different accounts, there should be no conflict when both streams are using the same subjects.
Given the expectation, what is the defect you are observing?
Instead, we saw the following error from rancher:
apparently the second stream failed to be created due to the overlapping subject space.
Is there a way in
stream.jetstream.nats.io/v1beta2
to directly refer to the account created by nats-server configuration file without usingaccount.jetstream.nats.io/v1beta2
.If there is a way, what is the correct setup? Is it only possible using certificates? What about nkey or plain user/password?