Skip to content

yoadey/nats-test

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Tool to test the data in a NATS instance during restarts

Setup

  1. Adapt the persistence class in your nats-values.yaml
  2. Deploy NATS to the cluster in the NATS namespace
helm repo add nats https://nats-io.github.io/k8s/helm/charts/
helm --kube-context <context> --namespace nats --install --create-namespace upgrade nats nats/nats --version 1.1.12 -f nats-values.yaml
  1. If there were already kvstores, you may need to delete them, they are automatically recreated:
nats kv rm <kvstorename> -f
  1. Deploy the nats-test by applying the deploy.yml file: kubectl --context <context> apply -f deploy.yml
  2. Scale the nats-test deployment and the restart-nats-statefulset to 1
  3. Monitor the output of the nats-test pod, as soon as it is out of sync, it will show the Message "KEY NOT FOUND: ..."
  4. Stop the test by scaling the nats-test deployment and the restart-nats-statefulset to 0
  5. Check issue by opening the nats-box and using the following command multiple times
nats kv ls testkv --trace
  1. Output should sometimes be Key1 and sometimes No keys found in bucket

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages