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
Cross-namespace references are gated by NatsReferenceGrant alone
A reference crosses namespaces only where a NatsReferenceGrant in the target namespace admits it, modelled on Gateway API’s ReferenceGrant and checked on every reconcile so that deleting a grant revokes what it admitted; withdrawing a grant to a trust object holds the NatsCluster at its last render instead (design §7). It replaced both an allow-list field on NatsAccount and a requester-RBAC check at admission, which needed a webhook and could not revoke. The name is not NatsGrant because NATS already grants permissions and imports.