Core workflow
7 min
scan kubegrade analyzes cluster resources and workload state events and signals configuration and policy posture iac / git definitions (when connected) purpose identify drift, risk, failures, or upgrade blockers build context for troubleshooting and change recommendations visualize kubegrade presents interactive views of cluster objects and dependencies service relationships warning states and impacted components relevant context for investigations propose pr kubegrade’s gitops agent drafts git native pull requests (for example, kubernetes manifests, helm values, or terraform changes) that encode the proposed upgrade or remediation steps, so teams can review, comment, and approve them in their existing git workflow what’s inside a pr includes concrete config changes plus human‑readable rationale and risk notes links back to the originating incident, cluster, or recommendation in kubegrade how this fits existing processes integrates with your current git provider and ci, so approvals, checks, and rollouts follow your normal process supports progressive rollout patterns (e g , staging first, then production) encoded directly in the pr content or labels approve kubegrade is designed to keep humans in the loop teams review proposed changes (never auto‑applied) safety checks and policy outcomes scope of impact execution plan / timing execute (gitops) changes are applied through your gitops process (e g , argo cd or flux), preserving auditability review controls provenance of change rollback paths