Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
JetStream subscriptions not working with k8s
See original GitHub issueJetStream subscriptions are not triggered when used inside k8s it works when I run it with docker-compose or locally but not when used inside k8s
Not sure if this issue should be opened on the NATS Server itself.
I checked with https://github.com/nats-io/nats-box I am able to subscribe and see messages
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (2 by maintainers)
Top Results From Across the Web
jetstream durable queue not working as expected #712 - GitHub
NATS/Jetstream are running on kubernetes v1.19.3+vmware.1. ... QueueSubscribeSync return filtered consumer not unique on workqueue stream .
Read more >Configuring JetStream - NATS Docs
To enable JetStream in a server we have to configure it at the top level first: ... JetStream will be enabled and if...
Read more >NATS Jetstream Technical Overview - YouTube
Tomasz was also one of the early adopters of Kubernetes while working in SAP and is using it extensively since then, often helping...
Read more >Kubernetes Deployment config for connecting to NATS event ...
So how could I solve the issue and connect to NATS without any problem? Any help would be appreciated. node.js · kubernetes ·...
Read more >JetStream - Dapr Docs
Create a NATS server. Self-Hosted; Kubernetes. You can run a NATS Server with JetStream enabled locally using ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The issue is you are using a queue Jetstream subscription with a new server and an old client…
Please update your client.
See https://github.com/nats-io/nats.js/releases/tag/v2.2.0
https://github.com/nats-io/nats-server/pull/2438#issue-712652418
https://github.com/nats-io/nats.js/issues/446