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

[svenfoo]

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 its 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]

Hey!

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

[svenfoo]

@Jarema Any progress on this? Can we help with this task?

[Jarema]

@samuelattwood will be picking this one really soon.
There will be some opportunity to contribute for sure, but Ieave it to Sam when and how :).

[ygabuev]

Hey @Jarema @samuelattwood ! Is there a timeline for this? We are looking forward to having this issue fixed and we can offer some help, but we would need some coordination on your side.

[Jarema]

Its already in progress, but it depends on 2.11 server relesse (and its pedantic mode feature).

[svenfoo]

We upgraded the nack chart to v0.28.0 and enabled the new "Control Loop" feature on the NACK operator. And as far as I can see this fixes the issue reported here. But you may want to keep this issue open until the feature is enabled by default.