Skip to content

docs: add "Running multiple reporters" section to k8s tutorial #259

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 1 commit into from
Jun 9, 2026
+13 −0
Merged

docs: add "Running multiple reporters" section to k8s tutorial #259

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 13 additions & 0 deletions tutorials/report_k8s_envs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,6 +166,19 @@ kosli snapshot k8s k8s-tutorial \
</Tab>
</Tabs>

## 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.

| 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. |

The rule of thumb: a single Kosli environment must have exactly one reporter feeding it.

## What you've accomplished

You have reported a snapshot of your Kubernetes cluster to Kosli. Kosli now tracks the running artifacts in that environment and will record changes as they happen.
Expand Down
Loading