Your environment-aware Upgrade Agent inside Claude Code—opening precise, review-ready IaC pull requests quickly and safely.
A few weeks ago, we introduced the Chkk Upgrade Agent + Upgrade Context Server. We showed how it identifies components requiring upgrades based on EOL, compatibility, and other criteria; recommends a compatible, stable target version (not just the latest); explains why the upgrade is warranted; and delivers an environment-specific PR creation workflow. This workflow comes equipped with source-grounded, task-specific agents for IaC pattern detection, Helm/CRD/RBAC diffs, ordering, and safety guardrails—while your Coding Assistant holds the pen and opens the PR.
Today, we’re announcing Chkk Upgrade Agent support for Claude Code. It works across 270+ open-source projects, including:
You can bring your own models—Claude 4, GPT-5, Gemini, or whatever your org already runs. There’s no lock-in, no retraining, and you can leverage existing enterprise contracts—keeping the same seats, tokens, and terms you’ve already negotiated with Anthropic, OpenAI, Google Cloud, and others. Your code stays inside your perimeter: Claude Code holds the pen.
The payoff is immediate: planned upgrades turn into review-ready PRs in minutes, not days; reviewers see rationale and risks inline; and execution windows stop slipping because upgrades are scoped, ordered, and auditable.
Coding Assistants (like Cursor, Claude, Gemini, GitHub Copilot, …) can write Terraform and Helm. What they lack is context: your live topology, the reasons for upgrading a component, IaC patterns used across K8s and OSS projects (Istio, Kafka, Keycloak, etc.), distro nuances, dependency edges, and whether “latest” is actually compatible for your stack.
The Chkk Upgrade Agent closes that gap by injecting the right context, at the right time, into your IDE via the Model Context Protocol (MCP). The result: fewer hand edits, faster reviews, and pull requests that are tightly scoped yet complete—with clear explanations of both why and what is being upgraded.
The Upgrade Agent is like a teammate inside your editor. It takes environment-aware context from Chkk and turns an approved Upgrade Plan into precise IaC edits. You hand it an upgrade_id; it fetches the plan, sets up a local scratchpad for traceability, locates the IaC root, and runs safety checks before touching anything. From there, it applies changes deterministically—adding files, patching templates and values, copying CRDs, and updating resources when schemas evolve.
When it’s done, you get a clear, PR-ready summary that explains what changed and why.
The difference lies in restraint and specificity. The agent scopes itself to what you actually run, respects your customizations, and prints auditable outcomes as it goes. It’s like a reliable teammate who knows your system inside and out.
The Upgrade Context Server bridges your Upgrade Plans and your IDE. It’s an MCP server that streams only the minimal relevant context, exactly when needed: a version compatible with your stack (not just “latest”), precise diffs and artifacts for your IaC pattern, and reviewer notes that unblock decisions—covering breaking changes, critical fixes, and key considerations.
Inside Claude Code, ask the Chkk Upgrade Agent to fetch Upgrade Context for the OSS project you’re about to modify—say, cert-manager or External Secrets Operator. The agent will:
Claude Code then applies the diff and opens the PR, with optional preflight and postflight checks to ensure code and running state remain aligned.
=> Read the User Guide for step-by-step setup and examples.
