Architecture decision records
Architecture decision records
0001
Three controllers, one API group each
2026-10-04
0002
No controller reads another’s group; shared kinds live in nats-operator.io
2026-10-04
0003
Trust roots through trust objects that hold a reference or literal values
2026-09-26
0004
One StatefulSet per NATS server
2026-09-28
0005
The Kubernetes cluster holds signing keys only; identities may stay offline
2026-09-28
0006
No supercluster resource; gateways are a property of NatsCluster
2026-09-28
0007
Cross-namespace references are gated by NatsReferenceGrant alone
2026-09-29
Three controllers, one API group each
The cluster, the auth plane and JetStream are three separately deployable controllers, each owning one API group, so that JetStream and auth management work against NATS clusters this project did not deploy and each part installs, is granted RBAC and is versioned on its own. A group marks one controller’s boundary rather than a count of kinds, which is why cluster.nats-operator.io holds NatsCluster alone and NatsCluster was not folded into the shared group.