Skip to content

docs: add Kubernetes reporter integration page#112

Open
mintlify[bot] wants to merge 1 commit intomainfrom
mintlify/kubernetes-reporter-1774683916
Open

docs: add Kubernetes reporter integration page#112
mintlify[bot] wants to merge 1 commit intomainfrom
mintlify/kubernetes-reporter-1774683916

Conversation

@mintlify
Copy link
Copy Markdown
Contributor

@mintlify mintlify bot commented Mar 28, 2026

Summary

  • Added a new Kubernetes page under Integrations that explains what the Kosli K8s reporter is, how it works inside a cluster, what it reports, namespace scoping options, and setup steps.
  • Added the page to the docs.json navigation under Integrations.

The page bridges the gap between the existing tutorial (step-by-step how-to) and the Helm chart reference (configuration options) by providing a conceptual overview of the reporter's purpose and architecture.

@mintlify mintlify bot requested a review from a team as a code owner March 28, 2026 07:45
@sofusalbertsen
Copy link
Copy Markdown
Contributor

I needed this for DB, dont know if it is universally applicable.

@mintlify
Copy link
Copy Markdown
Contributor Author

mintlify bot commented Mar 28, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
kosli 🟢 Ready View Preview Mar 28, 2026, 8:07 AM

@mbevc1 mbevc1 changed the title Add Kubernetes reporter integration page docs: add Kubernetes reporter integration page Mar 28, 2026
description: "Track what is running in your Kubernetes clusters by deploying the Kosli reporter, which periodically snapshots pod images and reports them to Kosli."
---

The Kosli Kubernetes reporter gives you continuous visibility into the artifacts running in your clusters. It runs as a lightweight CronJob that periodically scans the pods in your cluster (or a subset of namespaces), collects the container image digests, and sends that information to Kosli as an [environment snapshot](/getting_started/environments).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The Kosli Kubernetes reporter gives you continuous visibility into the artifacts running in your clusters. It runs as a lightweight CronJob that periodically scans the pods in your cluster (or a subset of namespaces), collects the container image digests, and sends that information to Kosli as an [environment snapshot](/getting_started/environments).
The Kosli Kubernetes reporter gives you continuous visibility into the artifacts running in your clusters. It runs as a lightweight `CronJob` that periodically scans the pods in your cluster (or a subset of namespaces), collects the container image digests, and sends that information to Kosli as an [environment snapshot](/getting_started/environments).

| **ServiceAccount & RBAC** | Grants the reporter read-only access to list pods — either cluster-wide or within specific namespaces. |
| **Secret reference** | Points to a Kubernetes Secret that holds your Kosli API token. |

Each time the CronJob fires, a short-lived pod starts, queries the Kubernetes API for running pods, extracts the container image digests and creation timestamps, and sends the data to Kosli. The pod then terminates. No data is stored inside the cluster.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Each time the CronJob fires, a short-lived pod starts, queries the Kubernetes API for running pods, extracts the container image digests and creation timestamps, and sends the data to Kosli. The pod then terminates. No data is stored inside the cluster.
Each time the `CronJob` fires, a short-lived pod starts, queries the Kubernetes API for running pods, extracts the container image digests and creation timestamps, and sends the data to Kosli. The pod then terminates. No data is stored inside the cluster.

Copy link
Copy Markdown
Contributor

@mbevc1 mbevc1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor comments, not a blocker. But looks good otherwise

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants