nats-io/nack

Issues

• Jetstream Stream CRD requires mirror, sources and placement

  #43 opened 3 years ago
  3

• Stream MaxBytes not set during create

  #40 opened 3 years ago
  3

• Support for NATS 2.4.0 new fields

  #38 opened 3 years ago
  2

• Add DeliverGroup to CRDs

  #37 opened 3 years ago
  1

• Support JetStream mirrors/data replication

  #36 opened 3 years ago
  2

• leadnodes unable to lookup for host and no such host

  #35 opened 3 years ago
  1

• release tag is inconsistent with docker hub tag

  #30 opened 3 years ago
  1

• jetstream.yml - [ is not respecting the storage value on the helm chart ]

  #28 opened 4 years ago
  2

• crd storage type mismatch

  #24 opened 4 years ago
  2

• Add metrics based horizontal autoscaling support for NATS cluster

  #22 opened 4 years ago
  0

• Need to designate the NATS server or account to create a stream after deployed the jetstream controller

  #21 opened 3 years ago
  5

• CRDs should represent the converged state in the cluster.

  #18 opened 4 years ago
  0

• Prevent ephemerals consumers creation

  #17 opened 4 years ago
  1

• Support MaxAckPending in consumers

  #14 opened 4 years ago
  0

• Extract NATS Operator service account token feature into its own controller

  #13 opened a year ago
  1

• Update jsm.go deps

  #12 opened a year ago
  1

• Support jetstream controller connecting to multiple jetstream instances

  #11 opened 3 years ago
  1

• Refine installation step to allow easier getting started

  #10 opened 4 years ago
  1

• Pull based consumer stuck with the first message

  #8 opened 4 years ago
  0

• Add TLS connection handling to jetstream-controller

  #6 opened 3 years ago
  1

• Add readiness/liveness endpoint

  #3 opened 4 years ago
  0

• Logo

  #1 opened 4 years ago
  0