Data handling & what leaves the cluster

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)