---
title: Core workflow
slug: core-workflow
createdAt: 2026-02-24T01:07:26.940Z
---

# 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