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 controller reads another’s group; shared kinds live in nats-operator.io
Every kind two controllers need (NatsConnection, NatsReferenceGrant, NatsOperatorTrust, NatsAccountTrust) lives in nats-operator.io, and no controller reads another controller’s group. The JetStream controller therefore has one mode: it reaches every NATS cluster, managed or not, through a NatsConnection whose credentials decide the account, and never reads NatsCluster or NatsAccount. Kind-tagged references into other groups (clusterRef: {kind: NatsCluster}, accountRef) and an auth controller that minted JetStream credentials were tried in the stories and dropped for this.
Consequences#
A balancer cannot see a rollout; it pauses per step through its own Settled gate instead of for the whole rollout.