Find the maintained successor to an old Helm chart

An old installation command points to a Helm chart that is no longer maintained. You need to find where the application is packaged now and whether it can replace the old installation safely. A chart is an installation package; the application it installs has its own project and release history. One can be retired while the other continues.

The old Helm stable and incubator repositories stopped development in November 2020. Their archives preserve earlier packages. Start with the application's current upstream installation guide, then compare the new package's settings, container images and data handling with the old deployment. An identical chart name is not enough to establish compatibility.

A four-part lookup

1. Recover the exact old chart URL and version from the release or deployment repository.
2. Find the application's current upstream installation documentation and identify the publisher it recommends.
3. Check the new chart's application version, values schema, resource names, CRDs and required images.
4. Classify the relationship: renamed chart, maintained continuation, alternative deployment, or no verified successor.

Examples that need different actions

The former prometheus-operator chart became kube-prometheus-stack, while Prometheus Operator remains one component. Ark became Velero. kube-lego gave way to cert-manager. Community ingress-nginx is retired and needs a different networking implementation. These relationships are not interchangeable: a rename, a new control plane and a different product each require different migration evidence.

Check what will happen to existing resources

A new chart can produce a different Service name, PVC template, selector or Secret. Compare manifests in a disposable environment and inspect ownership before changing a live release. An identical application name does not make the existing values file compatible. Export configuration and retain a known-good deployment artifact.

When there is no clear successor

Keep the old entry with an honest status and compare current tools by the original task. A stale commit date is a review prompt, not proof of retirement. A package remaining downloadable is not evidence of support. For persistent systems, select the target only after a restore rehearsal and define how post-cutover writes are recovered.

Use the resource directory for project context and upstream links. Read Bitnami distribution changes when source availability and image maintenance differ. This guide helps identify and assess a target; it does not certify every archived chart's migration.