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
The Kubernetes cluster holds signing keys only; identities may stay offline
A NATS operator’s identity key signs only its own JWT, and signing keys listed in the NATS operator and account JWTs sign everything else, including activation tokens. So NatsOperator.spec.jwt (signed offline) and an account’s publicKey replace identity seeds, and a Kubernetes cluster need hold only signing seeds, in Secrets that may be synced from an external store. The cost is that every NATS operator JWT change, which is also a supercluster-wide restart, needs the offline identity to re-sign it.