FAQ
8 min
security faq does kubegrade execute changes directly in my cluster? kubegrade supports controlled execution models and is designed to keep humans in the loop in gitops workflows, changes are proposed as prs and applied through your gitops system after review/merge ( kubegrade ) can kubegrade run in private or regulated environments? yes, kubegrade publicly positions support for cloud, on prem, and hybrid environments exact deployment architecture depends on your setup and requirements ( kubegrade ) what permissions does the agent need? permissions depend on enabled modules and whether you use read only or execution enabled workflows start with least privilege and expand only as needed does kubegrade collect secrets? kubegrade should not collect secret values unless explicitly required for a configured integration secret handling behavior must be documented by deployment mode and integration pricing/billing faq (optional) how is kubegrade priced? document your actual pricing model only (e g , by cluster, node, seat, or enterprise plan) if still evolving, say so and direct to sales is on prem pricing different from saas? typically yes, because support, deployment complexity, and infrastructure requirements differ publish only confirmed commercial policy are there limits on clusters or users? list plan based limits here and link to the limits & quotas page troubleshooting faq why is my cluster showing as disconnected? common causes agent not running network egress blocked tls/certificate trust issue invalid credentials/token proxy misconfiguration why can’t kubegrade generate a pr? common causes git repo not connected insufficient repo permissions path mapping not configured policy blocked pr generation unsupported repo layout edge case why is drift reported for fields we don’t manage? you may need exclusions/suppression rules for provider managed or runtime generated fields why is execution blocked after approval? a second gate may still apply maintenance window closed policy check failed on re validation gitops sync restrictions environment freeze window