Operations
The deployment topology, the settings that must agree across services, and the failure modes that follow when they do not.
-
Every service in the topology, the ports it publishes, and the certificates and environment it expects.
-
The three topics, their retention and partitioning, and the per-role principal that may touch each one.
-
The six-layer precedence chain every service shares, the per-platform paths, and credential protection.
-
The single pipeline: which job builds what, when each one runs, and what a release tag produces.
-
The short list of settings that must agree across services, and what breaks when they do not.
Start here if something is wrong
| Symptom | Look at |
|---|---|
| Every service fails at once | redpanda-init logs — it creates users, ACLs and topics, and everything else assumes it succeeded |
| Broker will not start | Certificates — there is no self-signed fallback |
| Agent connects but no events land | ACLs — the agent principal may write RawEvents only |
| Agent rejected at the fleet hub | API_KEY_HASH unset; FleetServer refuses every agent when no hashes are configured |
| Process nodes carry only a PID | Invariants — carry-forward window mismatch |
| History splits at a restart | SkipIdentityRestore is on, or the changelog is disabled |
| Memory climbing on the processor | MaxTrackedIdentities set to 0, which disables the cap |
| A build job did not run on a branch or merge request | CI — path filters skip components the change did not touch |