nack: NACK fails to create a stream with kustomize and namespacing

I’ve installed CRDs, NACK using Helm chart, and created a stream in the same namespace as NACK and NATS server.

In logs, I see that NACK client opened a connection to the NATS server. Then nothing changes. I don’s see any stream in NATS using its command-tool.

# NACK log
I1222 17:45:47.333603       1 main.go:117] Starting /jetstream-controller v...

# NATS log
[6] 2021/12/22 17:45:46.411918 [DBG] 10.233.122.229:39318 - cid:24 - "v1.12.1:go:jetstream-controller" - Client connection closed: Client Closed
[6] 2021/12/22 17:45:52.336792 [DBG] 10.233.68.1:56700 - cid:25 - Client connection created
[6] 2021/12/22 17:45:54.605762 [DBG] 10.233.68.1:56700 - cid:25 - "v1.12.1:go:jetstream-controller" - Client Ping Timer

# stream state is empty
kubectl get streams -n testing01
NAME                            STATE   STREAM NAME   SUBJECTS
nats-back-back-reliable-strem           reliable      ["scope.*.*"]

# port forwarding
nats str list -s localhost:59286
No Streams defined

apiVersion: jetstream.nats.io/v1beta2
kind: Stream
metadata:
  name: nats-back-back-reliable-strem
spec:
  name: reliable
  subjects:
  - "scope.*.*"
  storage: memory
  retention: limits
  discard: old
  maxAge: 1h
  maxBytes: 1048576
  replicas: 1

Definition of the stream.

jetstream:
  enabled: true
  nats:
    url: nats://nats-back-back-internal-lb:4222

namespaced: true

NACK config.

nats:
  image: nats:2.6.5-alpine3.14
  resources:
    limits:
      cpu: 0.1
      memory: 300Mi
    requests:
      cpu: 0.1
      memory: 300Mi
  logging:
    debug: true

  jetstream:
      enabled: true

      memStorage:
        enabled: true
        size: 1Gi

exporter:
  enabled: true
  image: natsio/prometheus-nats-exporter:0.9.0
  serviceMonitor:
    enabled: true

cluster:
  enabled: false

natsbox:
  enabled: false

auth:
  enabled: false

NATS server config.

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 18 (8 by maintainers)

Most upvoted comments

Yes, I see now. I’ve missed that Kustomize caches previously installed Helm chart in “charts” directory. After removing the cache directory, a new version of NACK get installed and stream has been created. Thanks.

manifest on Feb 2, 2022

With the latest commit it works 😃 I was able to create a stream. Thank you. When can we expect a release with these changes?

k get stream -n testing01

NAMESPACE   NAME                             STATE     STREAM NAME   SUBJECTS
testing01   nats-back-back-reliable-stream   Created   reliable      ["scope.*.*"]

nats str list -s localhost:54600
╭───────────────────────────────────────────────────────────────────────────────╮
│                                    Streams                                    │
├──────────┬─────────────┬─────────────────────┬──────────┬──────┬──────────────┤
│ Name     │ Description │ Created             │ Messages │ Size │ Last Message │
├──────────┼─────────────┼─────────────────────┼──────────┼──────┼──────────────┤
│ reliable │             │ 2022-01-18 16:01:31 │ 0        │ 0 B  │ never        │
╰──────────┴─────────────┴─────────────────────┴──────────┴──────┴──────────────╯

k logs -f po/nack-8885cfddc-jkprl -n testing01

I0118 16:16:11.945031       1 main.go:117] Starting /jetstream-controller v...
I0118 16:16:31.239923       1 event.go:285] Event(v1.ObjectReference{Kind:"Stream", Namespace:"testing01", Name:"nats-back-back-reliable-stream", UID:"08c4c36c-9f93-41cf-9a09-b228025eb947", APIVersion:"jetstream.nats.io/v1beta2", ResourceVersion:"151937610", FieldPath:""}): type: 'Normal' reason: 'Creating' Creating stream "reliable"
I0118 16:16:31.270959       1 event.go:285] Event(v1.ObjectReference{Kind:"Stream", Namespace:"testing01", Name:"nats-back-back-reliable-stream", UID:"08c4c36c-9f93-41cf-9a09-b228025eb947", APIVersion:"jetstream.nats.io/v1beta2", ResourceVersion:"151937610", FieldPath:""}): type: 'Normal' reason: 'Created' Created stream "reliable"

manifest on Jan 18, 2022