Chart LedgerView source ↗
HELM MIGRATION REVIEW / SOURCE-LINKED EVIDENCE

Trace changes.
Read the source.

Turn a deployment diff and migration guide into a source-linked review brief.

An open-weight model orders the reading. You make the upgrade decision.

01 / TRY THE CONTROLLED EXAMPLE

A green chart check.
A readiness path that changed.

Kong 2.25.0 → 2.26.0. See the diff, relevant migration passages, and the controller question the inputs cannot answer.

Real CPU inference. No model API key.
REVIEW ACROSS SKIPPED RELEASES

One upgrade.
Several migration questions.

Kong 2.18.0 → 2.26.0. Select the intervening release notes and general guidance automatically, then prepare separate reading for the readiness and filesystem changes.

Controlled chart renders. No live-cluster approval.
02 / BRING YOUR OWN EVIDENCE

Prepare your review.

One Deployment. Automatic version-range selection or an explicit guide section. Separate reading for each change.

Files are sent to this server for processing and deleted from its temporary directory afterward. No hosted model API is called. Use sanitized inputs; do not upload secrets.

Know what this brief covers.

Images, HTTP probe paths and ports, and read-only-root settings in one selected Deployment. It cannot establish live-cluster state, collect every version's migration warning, or approve an upgrade. Sources supplied by you are identified by their bytes, not authenticated as publisher statements.