<p>I have followed instructions from <a href="https://blog.alexellis.io/test-drive-k3s-on-raspberry-pi/" rel="nofollow noreferrer">this blog</a> post to set up a k3s cluster on a couple of raspberry pi 4:</p>

<p>I'm now trying to get my hands dirty with traefik as front, but I'm having issues with the way it has been deployed as a 'HelmChart' I think.</p>

<p>From the <a href="https://github.com/rancher/k3s/blob/master/README.md" rel="nofollow noreferrer">k3s docs</a></p>

<blockquote>
  <p>It is also possible to deploy Helm charts. k3s supports a CRD
  controller for installing charts. A YAML file specification can look
  as following (example taken from
  <code>/var/lib/rancher/k3s/server/manifests/traefik.yaml</code>):</p>
</blockquote>

<p>So I have been starting up my k3s with the <code>--no-deploy traefik</code> option to manually add it with settings. So I therefore manually apply a yaml like this:</p>

<pre><code>apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: traefik
  namespace: kube-system
spec:
  chart: https://%{KUBERNETES_API}%/static/charts/traefik-1.64.0.tgz
  set:
    rbac.enabled: "true"
    ssl.enabled: "true"
    kubernetes.ingressEndpoint.useDefaultPublishedService: "true"
    dashboard:
      enabled: true
      domain: "traefik.k3s1.local"
</code></pre>

<p>But when trying to iterate over settings to get it working as I want, I'm having trouble tearing it down. If I try <code>kubectl delete -f</code> on this yaml it just hangs indefinitely. And I can't seem to find a clean way to delete all the resources manually either.</p>

<p>I've been resorting now to just reinstall my entire cluster over and over because I can't seem to cleanup properly.</p>

<p>Is there a way to delete all the resources created by a chart like this without the <code>helm</code> cli (which I don't even have)?</p>

Viktor Hedefalk
<p>Are you sure that <code>kubectl delete -f</code> is hanging?</p>

<p>I had the same issue as you and it seemed like <code>kubectl delete -f</code> was hanging, but it was really just taking a long time.</p>

<p>As far as I can tell, when you issue the <code>kubectl delete -f</code> a pod in the <code>kube-system</code> namespace with a name of <code>helm-delete-*</code> should spin up and try to delete the resources deployed via helm.  You can get the full name of that container by running <code>kubectl -n kube-system get pods</code>, find the one with <code>kube-delete-&lt;name of yaml&gt;-&lt;id&gt;</code>.  Then use the pod name to look at the logs using <code>kubectl -n kube-system logs kube-delete-&lt;name of yaml&gt;-&lt;id&gt;</code>.</p>

<p>An example of what I did was:</p>

<pre><code>kubectl delete -f jenkins.yaml # seems to hang
kubectl -n kube-system get pods # look at pods in kube-system namespace
kubectl -n kube-system logs helm-delete-jenkins-wkjct # look at the delete logs
</code></pre>
