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
Trust roots through trust objects that hold a reference or literal values
Every NatsCluster with an auth plane reaches its trust roots through auth.trustRef to a NatsOperatorTrust, and a leaf binds accounts through NatsAccountTrust. Each trust object holds either a reference to the live NatsOperator or NatsAccount in the same Kubernetes cluster, whose status the auth controller fills, or literal JWTs and keys copied by GitOps where no auth controller runs. This replaced three ways to get trust (auth.operatorRef, a supercluster resource’s inline trust, per-leaf literals) with one, and keeps the cluster controller from reading the auth group.