The three event buses are off by default, because most tenants do not need them and each one uses CPU, memory and a volume per pod. Their namespaces and network policies are always present, so turning one on needs no policy change.
| Bus | Variable | Use it for |
|---|---|---|
| NATS JetStream | nats_enabled | Durable, replayable streams between services. The first choice when a bus is needed. |
| Valkey with Sentinel | valkey_enabled | Sessions, rate limits and caches |
| Kafka (Strimzi) | kafka_enabled | Data pipelines, change data capture and long-term event retention |
Valkey refuses writes while none of its replicas is in sync with the primary (min-replicas-to-write 1, min-replicas-max-lag 10). A master cut off from its replicas therefore cannot accept writes that a Sentinel failover would later throw away. The cost is that Valkey stops taking writes if both replicas are down.
#Turn one on
Run the bootstrap with the variable set to true. For NATS:
ansible-playbook -i tenant-workload/bootstrap/hosts.ini tenant-workload/bootstrap/bedrock-bootstrap.yml -e nats_enabled=trueSeveral at once:
ansible-playbook -i tenant-workload/bootstrap/hosts.ini tenant-workload/bootstrap/bedrock-bootstrap.yml \
-e nats_enabled=true -e valkey_enabled=trueThe bootstrap leaves everything that is already installed as it is and waits for every pod of the bus to be ready.
The bootstrap refuses to run once a failover has happened, because it would turn the new primary back into a replica. After a failover, turn NATS or Valkey on by applying its manifest directly, since its OpenBao role, its password and its network policy are already in place:
kubectl apply -f tenant-workload/event-buses/nats.yaml
kubectl apply -f tenant-workload/event-buses/valkey.yamlKafka also needs the Strimzi operator, which the bootstrap downloads, checks and patches first. Follow the Strimzi and Kafka tasks in tenant-workload/bootstrap/bedrock-bootstrap.yml by hand.
#Check it
kubectl -n nats get podsOne pod per node, all Running. For Valkey use the valkey namespace and for Kafka the kafka namespace.
#Let an application use it
No platform component talks to the buses, so their network policies only admit traffic from their own namespace. When an application needs a bus, add an ingress rule to the bus’s policy in tenant-workload/netpols/event-buses.yaml that names the application’s pods, and an egress rule in the application’s own policy that names the bus. Both sides have to allow the flow.
The bootstrap makes the NATS and Valkey passwords once and stores them in OpenBao. The pods read them as files through the Secrets Store CSI driver. An application reads the Valkey password at apps/valkey/auth and the NATS app user’s password at apps/nats/app, through an OpenBao role of its own. Kafka’s users are made by Strimzi.
#Make it permanent
The -e flag applies to one run. To keep a bus on for every future deploy, set its variable to true in the vars block of the second play in tenant-workload/bootstrap/bedrock-bootstrap.yml.