Skip to content

docs: clarify k8s multi-reporter impact on snapshots #260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dangrondahl merged 5 commits into from
Jun 9, 2026
+13 −8
Merged

docs: clarify k8s multi-reporter impact on snapshots #260

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
88b4f95
docs: clarify k8s multi-reporter impact on snapshots
dangrondahl Jun 9, 2026
1e92d03
docs: split multi-reporter warning into bulleted callout
dangrondahl Jun 9, 2026
93836cf
style: match bullet style to rest of file
dangrondahl Jun 9, 2026
cdb24b0
docs: replace emoji with Yes/No in reporter table
dangrondahl Jun 9, 2026
3ff8c94
docs: rename Works? column to Supported
dangrondahl Jun 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 13 additions & 8 deletions tutorials/report_k8s_envs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,16 +168,21 @@ kosli snapshot k8s k8s-tutorial \

## Running multiple reporters

If you are considering running more than one reporter against the same cluster, the table below summarizes which setups are safe and which will cause data loss.
If you are considering running more than one reporter against the same cluster, the table below summarizes which setups produce meaningful snapshots and which don't.

| Scenario | Safe? |
| --- | --- |
| Two orgs, separate environments, overlapping namespaces | **Safe.** Different environments → separate snapshots. |
| One org, two environments, overlapping namespaces | **Safe.** Same as above. |
| One org, **same environment**, two reporters with overlapping namespaces | **Broken.** Snapshots toggle back and forth. Data is lost on each report. |
| One org, same environment, two reporters with **disjoint** namespaces | **Still broken.** Each report wipes the namespaces the other reporter owns. The reporter must be the sole source for the environment. |
| Scenario | Supported | Explanation |
| :--- | :---: | :--- |
| Two orgs, separate environments, overlapping namespaces | Yes | Different environments → independent snapshots. |
| One org, two environments, overlapping namespaces | Yes | Same as above. |
Comment thread
dangrondahl marked this conversation as resolved.
Comment thread
dangrondahl marked this conversation as resolved.
| One org, **same environment**, two reporters with overlapping namespaces | No | Snapshots toggle between each reporter's view. No data is deleted, but diffs between consecutive snapshots become meaningless. |
| One org, same environment, two reporters with **disjoint** namespaces | No | Each snapshot only reflects one reporter's namespaces, so diffs compare unrelated scopes. |

The rule of thumb: a single Kosli environment must have exactly one reporter feeding it.
<Warning>
A single Kosli environment must have exactly one reporter feeding it. Snapshots are never overwritten or deleted, but if two reporters take turns updating the same environment:

* Diffs between consecutive snapshots compare unrelated views of the cluster.
* The environment history shows artifacts continuously stopping and starting as each report toggles which namespaces are visible.
</Warning>

## What you've accomplished

Expand Down