The repo had accreted one estate's accounts, topics and prose. An application's
account and its topics belong to the application, whose own repo says what it
may read and write — so that adding or removing the application adds or removes
its access.
What is left is the cluster, the admin and smoke-test accounts, the
cross-namespace credentials store, and the pattern to copy.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The README described the cluster as it was before events existed: no declared
topics, no consumer, and no way for another namespace to reach a password
Strimzi keeps here.
The events themselves are specified by their producer, not here — this repo
owns the cluster, not the contract.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Strimzi 1.2.0 supports 4.2.0 through 4.3.1; the manifest still asked for 4.1.0,
so the cluster sat NotReady with the reason only visible in the Kafka CR's
status — the operator logs said nothing. Pinned to 4.3.1, and metadataVersion
removed rather than guessed: the operator derives it, and a stale spelling there
is the same failure one release later.
Adds a KafkaUser for classic-models-api: Write and Describe on the
classic-models. prefix, and no Read. It publishes domain events and consumes
nothing, and a producer that can read every topic exfiltrates every other
domain's events if it is ever compromised.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Stéphane Tailland