Data handling & what leaves the cluster
2 min
Overview
Kubegrade uses a minimum necessary data model, with deployment-mode differences.
Typical data used by Kubegrade
- Kubernetes object metadata and configuration state
- Events / status conditions
- Health and dependency context
- Workflow execution metadata
- Optional integration metadata (Git/IaC references, alert identifiers)
What may leave the cluster (SaaS / hybrid)
Depending on configuration:
- Telemetry metadata
- Resource state summaries
- Policy/drift findings
- Workflow request/response metadata
- Optional logs/diagnostic snippets (if enabled)
What should be explicitly documented by deployment mode
- Whether payloads include object specs vs metadata only
- Whether secrets are collected (recommended: no secret values)
- Retention periods
- Encryption in transit / at rest
- Regional hosting options (if any)