This message was deleted.
# k3sa
adamant-kite-43734
12/01/2025, 4:12 PMThis message was deleted.
c
creamy-pencil-82913
12/01/2025, 5:11 PMwell, don’t use multiple controllers to manage the same resources
creamy-pencil-82913
12/01/2025, 5:14 PMBut, if you for some reason want to keep the HelmChart resource around but stop the helm controller syncing it, see https://github.com/k3s-io/helm-controller/pull/137
• Adds support forannotation. HelmChart resources with this annotation will no longer be managed by the Helm controller, and can safely be updated or deleted without the Helm controller triggering any Jobs to install/update/delete the chart.<http://helmcharts.helm.cattle.io/unmanaged|helmcharts.helm.cattle.io/unmanaged>
• This is intended for use when an administrator wants to begin managing a Helm releases via another tool, such as Fleet, ArgoCD, or manual invocation of the Helm CLI tools, and wants to ensure that the embedded Helm controller no longer mucks about with the current release.
a
astonishing-accountant-28604
12/01/2025, 5:50 PMI don't want have multiple controllers managing the same resources, I want to safely get rid of the HelmChart. This looks right, the description says I can delete the HelmChart can be deleted with this annotation in place. Thanks, I'll test it.
32 Views