1
Onboard & register a cluster
What happens: Chkk’s Kubernetes Connector discovers resources, versions, and packaging patterns—forming the inventory foundation for all follow-on analysis.
- Chkk CLI
- Chkk Dashboard
2
Generate an Upgrade Assessment
What happens: Get a targeted view of upgrade candidates, EOLs, incompatibilities, and recommended paths so teams know where to focus first.
- Chkk CLI
- Chkk Dashboard
3
Request an Upgrade Template
What happens: Ask Chkk for a Project-specific Upgrade Template (e.g., cert-manager, ExternalDNS). Templates encode the safe path—including guardrails, checks, and strategy (in-place, canary/blue-green).
- Chkk Dashboard
4
Approve the Upgrade Template
What happens: Designated owners review and approve before anything becomes actionable, ensuring single-threaded, accountable governance.
- Chkk Dashboard
5
Instantiate an Upgrade Plan
What happens: From the approved Template, create a Plan scoped to a specific cluster/env. The Plan becomes the source of truth for the upcoming change.
- Chkk Dashboard
6
Review the Upgrade Plan
What happens: See the rationale (EOL, breaking changes, bug/security fixes, notable features) and the precise steps the agent will take—so reviewers understand scope and risk up front.
- Chkk Dashboard
7
Generate the IaC Pull Request
What happens: In your IDE, the Upgrade Agent fetches Upgrade Context from the Plan via the MCP server, detects your IaC pattern, applies targeted diffs (Helm/Kustomize/YAML), and prepares a ready-to-review PR.
- Cursor
- Claude Code
- Chkk Dashboard