Public Preview. Initial support focuses on Helm-based IaC across 260+ open-source projects. First IDE integration: Cursor x Chkk.

​
What is Upgrade Context Server (MCP) + Upgrade Agent?

Upgrading an add-on or application service is rarely a simple version bump. Between releases, Helm charts evolve, values.yaml options change, CRDs rotate, and templates shift. Manually diffing upstream and stitching edits into your IaC is slow and error-prone. Chkk Upgrade Context Server (MCP) connects your Chkk Upgrade Plan (grounded in your environment and policies) to your IDE via the Model Context Protocol. It vends just-enough, just-in-time context: compatible target versions, environment-specific diffs, and reviewer notes (breaking changes, security fixes, notable features). The Upgrade Agent consumes that context and applies the required edits to your IaC (Helm today), preserving your customizations and opening a focused PR you can review and merge. Why it matters
  • Choose versions that hold in prod. Targets are computed against your constraints and policies—not simply “latest.”
  • Edits are environment-aware and deterministic. Diffs are scoped to what you actually run, ordered for safe apply, and auditable.
  • Reviewer context is built-in. Breaking changes, compatibility notes, and critical fixes appear next to the change.

​
How it fits with Templates & Plans

Chkk lets you request an Add-on or Application Service Upgrade Template—a curated, pre-verified upgrade workflow that captures exact steps, constraints, and diffs for your environment. Create/approve a template in the Chkk Dashboard (see Requesting an Upgrade Template), then instantiate an Add-on or Application Service Upgrade Plan. Upgrade Context Server (MCP) turns that Upgrade Plan into actionable context (specifications, diffs, and reviewer notes) for the Upgrade Agent running in your IDE.

​
Supported today (Public Preview)

  • IaC format: Helm charts (templates, values, chart metadata, CRDs). Terraform, Kustomize, raw YAML, Jsonnet and others are on the roadmap.
  • IDE / Coding assistant: Cursor x Chkk (MCP). Claude Code, GitHub Copilot, and other MCP-capable IDEs coming soon.
  • Ecosystem coverage (examples): Networking (Istio, Cilium), Databases (PostgreSQL, Redis), Batch/Data Jobs (Argo Workflows, Jenkins), Streams (Kafka, RabbitMQ), Observability (Datadog, Grafana), Security (cert-manager, Kyverno), Autoscaling (Karpenter, KEDA), Dev Tooling (Argo CD, Bitbucket), and more.

​
FAQs

What is an Add-on or Application Service Upgrade Plan? An AI-curated workflow for a specific Addon, Application Service, or Kubernetes Operator across one or more clusters, instantiated from an Upgrade Template. See Glossary. What is the upgrade_id and why does the agent need it? upgrade_id is the natural key for your Upgrade Plan. The agent uses it to fetch the exact, environment-specific context (target version, diffs, artifacts, reviewer notes) for your cluster(s)—not generic upstream guidance. Which IDEs and coding assistants are supported? Cursor x Chkk is available in Public Preview. Support for Claude Code, GitHub Copilot, and other MCP-capable IDEs is coming soon. Which IaC patterns/formats are supported? Helm charts are supported today (templates, values, chart metadata, CRDs). We’re expanding to Terraform, Kustomize overlays, raw Kubernetes YAML, Jsonnet, and others. Where does temporary data go, and can I delete it? Into the Scratchpad (by default under .chkk/scratchpad/ in the repo). It’s ignored by Git and safe to delete at any time. Does the agent change my running cluster? No. It edits your IaC locally and opens a PR. Any apply/rollout steps are up to your CI/CD and change-management process. Do I have to use a specific “first prompt”? No—use natural language. In Cursor, instruct your assistant to use the Chkk upgrade agent and ask you for the upgrade_id to begin.

​
Common Variations & Edge Cases

  • Multiple charts matching the same name/version → you choose explicitly (no guessing).
  • Missing or read-only files → the agent fails fast with a complete list; nothing partial is committed.
  • Network issues → the agent stops early; no edits attempted.
  • Unsupported IaC patterns → Helm is supported today; other formats are on the way.

​
Getting started

  1. Create an Upgrade Plan. Instantiate an Add-on or Application Service Upgrade Plan from an approved Template (how-to). If needed, request a new Template (instructions).
  2. Enable the MCP server in your IDE. In Cursor, add the Chkk Upgrade Context MCP server.
  3. Run the workflow. In your editor chat: “Use the Chkk upgrade agent to apply the IaC changes. Start by asking for the upgrade ID.” Provide the upgrade_id when prompted, review the preflight, and let the agent apply the plan and generate the PR summary.