NACK does not handle a restart of the NATS server(s) - Githubissues

nats-io / nack

NATS Controllers for Kubernetes (NACK)

Apache License 2.0

155 stars 61 forks source link

NACK does not handle a restart of the NATS server(s) #202

Open svenfoo opened 1 week ago

svenfoo commented 1 week ago

What version were you using?

nack chart 0.26.1 (natsio/jetstream-controller:0.15.1) nats chart 1.2.4 (nats:2.10.20-alpine)

What environment was the server running in?

Linux, k3s

Is this defect reproducible?

Set up the NATS server with JetStream, but select the memory backend, not file based streams.
Define some streams and consumers that NACK should handle.

Up until here this works fine. The NATS server starts, NACK creates the streams and consumers.

Now restart the NATS server.

Given the capability you are leveraging, describe your expectation?

I would expect NACK to realize that NATS was restarted and that it needs to do it's job of creating the configured resources.

Given the expectation, what is the defect you are observing?

Nothing happens. The configured resources are only recreated after manually restarting NACK.

Jarema commented 1 week ago

Hey!

We are working on NACK having proper control loop. That will address the issue.