docs: add Kubernetes reporter integration page#112
docs: add Kubernetes reporter integration page#112mintlify[bot] wants to merge 1 commit intomainfrom
Conversation
Generated-By: mintlify-agent
|
I needed this for DB, dont know if it is universally applicable. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
mbevc1
changed the title
| 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). |
There was a problem hiding this comment.
| 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. |
There was a problem hiding this comment.
| 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. |
mbevc1
left a comment
mbevc1
left a comment
There was a problem hiding this comment.
Minor comments, not a blocker. But looks good otherwise
|
@sofusalbertsen, isn't there a big overlap between this and this page: https://kosli.mintlify.app/tutorials/report_k8s_envs |
Maybe that's fine, as this is a bit more elaborate. We just need to be aware that we kind of having two tutorials covering the same, but with slight differences. |
Also perhaps worth thinking what's the source of truth and maybe we could just dropped a link in one of those places 🤔 |
3 participants
Summary
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.