Skip to content

Commit b2e7765

Browse files
committed
docs(backups): the kafka-metadata helper execs a CLI Pod, not a throwaway one
Assisted-by: LLM Signed-off-by: IvanHunters <[email protected]>
1 parent e146f43 commit b2e7765

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎examples/backups/kafka-metadata/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ The platform default backups stack must be installed: the `backupstrategy-contro
1818

1919
## Flow
2020

21-
- `00-helpers.sh` — shared bash helpers (waiters, kafka seed/verify via a throwaway CLI pod, the demo strategy derivation + S3 CA copy).
21+
- `00-helpers.sh` — shared bash helpers (waiters, kafka seed/verify via a long-lived CLI pod it execs into, the demo strategy derivation + S3 CA copy).
2222
- `03-backupclass.yaml` — the demo `BackupClass` (`kafka-metadata`) mapping `Kafka` to the derived `kafka-strategy-default`.
2323
- `05-kafka-src.yaml` — the source application (no `backup:` block; the strategy carries the coordinates).
2424
- `10-backupjob-adhoc.yaml` — an ad-hoc `BackupJob` routed to the demo `kafka-metadata` BackupClass.

0 commit comments

Comments
 (0)