From 88b4f95dbb571beab77079521dd3ac2b4dc14050 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dan=20Gr=C3=B8ndahl?= Date: Tue, 9 Jun 2026 10:27:55 +0200 Subject: [PATCH 1/5] docs: clarify k8s multi-reporter impact on snapshots Reword the "Running multiple reporters" table to correctly describe what happens when two reporters target the same environment: snapshots are not deleted, but diffs between them compare unrelated scopes and the environment history shows artifacts flapping between reports. --- tutorials/report_k8s_envs.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/tutorials/report_k8s_envs.md b/tutorials/report_k8s_envs.md index b86ecf4..80c9fa1 100644 --- a/tutorials/report_k8s_envs.md +++ b/tutorials/report_k8s_envs.md @@ -168,16 +168,16 @@ 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 | Works? | Explanation | +| :--- | :---: | :--- | +| Two orgs, separate environments, overlapping namespaces | ✅ | Different environments → independent snapshots. | +| One org, two environments, overlapping namespaces | ✅ | Same as above. | +| One org, **same environment**, two reporters with overlapping namespaces | ❌ | 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 | ❌ | Each snapshot only reflects one reporter's namespaces, so diffs compare unrelated scopes. 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. +The rule of thumb: 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, the diffs between snapshots compare unrelated views of the cluster and the environment history will show artifacts continuously stopping and starting as each report toggles which namespaces are visible. ## What you've accomplished From 1e92d03fce5e4bc77664920b8251c88a0388c7a8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dan=20Gr=C3=B8ndahl?= Date: Tue, 9 Jun 2026 10:30:54 +0200 Subject: [PATCH 2/5] docs: split multi-reporter warning into bulleted callout --- tutorials/report_k8s_envs.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/tutorials/report_k8s_envs.md b/tutorials/report_k8s_envs.md index 80c9fa1..18dc4e6 100644 --- a/tutorials/report_k8s_envs.md +++ b/tutorials/report_k8s_envs.md @@ -177,7 +177,12 @@ If you are considering running more than one reporter against the same cluster, | One org, **same environment**, two reporters with overlapping namespaces | ❌ | 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 | ❌ | Each snapshot only reflects one reporter's namespaces, so diffs compare unrelated scopes. 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. Snapshots are never overwritten or deleted, but if two reporters take turns updating the same environment, the diffs between snapshots compare unrelated views of the cluster and the environment history will show artifacts continuously stopping and starting as each report toggles which namespaces are visible. + +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. + ## What you've accomplished From 93836cfa4cb7eb692b293bbe881a92d136590e74 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dan=20Gr=C3=B8ndahl?= Date: Tue, 9 Jun 2026 10:31:21 +0200 Subject: [PATCH 3/5] style: match bullet style to rest of file --- tutorials/report_k8s_envs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tutorials/report_k8s_envs.md b/tutorials/report_k8s_envs.md index 18dc4e6..1782e75 100644 --- a/tutorials/report_k8s_envs.md +++ b/tutorials/report_k8s_envs.md @@ -180,8 +180,8 @@ If you are considering running more than one reporter against the same cluster, 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. +* 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. ## What you've accomplished From cdb24b0190ca93ef8f8138c44b9ad3ee75b7ec15 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dan=20Gr=C3=B8ndahl?= Date: Tue, 9 Jun 2026 10:46:55 +0200 Subject: [PATCH 4/5] docs: replace emoji with Yes/No in reporter table --- tutorials/report_k8s_envs.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tutorials/report_k8s_envs.md b/tutorials/report_k8s_envs.md index 1782e75..1a4dc05 100644 --- a/tutorials/report_k8s_envs.md +++ b/tutorials/report_k8s_envs.md @@ -172,10 +172,10 @@ If you are considering running more than one reporter against the same cluster, | Scenario | Works? | Explanation | | :--- | :---: | :--- | -| Two orgs, separate environments, overlapping namespaces | ✅ | Different environments → independent snapshots. | -| One org, two environments, overlapping namespaces | ✅ | Same as above. | -| One org, **same environment**, two reporters with overlapping namespaces | ❌ | 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 | ❌ | Each snapshot only reflects one reporter's namespaces, so diffs compare unrelated scopes. The reporter must be the sole source for the environment. | +| Two orgs, separate environments, overlapping namespaces | Yes | Different environments → independent snapshots. | +| One org, two environments, overlapping namespaces | Yes | Same as above. | +| 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. | 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: From 3ff8c941485fb4eb4eeffa293f0876c9bef2c2f4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dan=20Gr=C3=B8ndahl?= Date: Tue, 9 Jun 2026 10:50:24 +0200 Subject: [PATCH 5/5] docs: rename Works? column to Supported --- tutorials/report_k8s_envs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorials/report_k8s_envs.md b/tutorials/report_k8s_envs.md index 1a4dc05..31a2b22 100644 --- a/tutorials/report_k8s_envs.md +++ b/tutorials/report_k8s_envs.md @@ -170,7 +170,7 @@ kosli snapshot k8s k8s-tutorial \ 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 | Works? | Explanation | +| Scenario | Supported | Explanation | | :--- | :---: | :--- | | Two orgs, separate environments, overlapping namespaces | Yes | Different environments → independent snapshots. | | One org, two environments, overlapping namespaces | Yes | Same as above. |