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
No supercluster resource; gateways are a property of NatsCluster
Each NatsCluster carries gateway.remotes and gateway.discovery, as nats-server’s own gateway config does, and the supercluster is what those lists form. A NatsSupercluster kind was drafted and dropped: it created nothing and only replicated a member list, which GitOps already replicates, and its name read like something that runs. The same list sits in every member and is kept alike outside the API.