Live data from Hacker News

Show HN: K8s Cleaner – Roomba for Kubernetes

sveltos.projectsveltos.io

1–10 of 64 posts

Show HN: K8s Cleaner – Roomba for Kubernetes

#1
Hello HN community!

I'm excited to share K8s Cleaner, a tool designed to help you clean up your Kubernetes clusters.

As Kubernetes environments grow, they often accumulate unused resources, leading to confusion, waste, and clutter. K8s-cleaner simplifies the process of identifying and removing unnecessary components.

The tool scans your Kubernetes clusters for unused or orphaned resources—including pods, services, ingresses, and secrets—and removes them safely. You can fully customize which resources to scan and delete, maintaining complete control over what stays and what goes.

Getting Started:

Visit https://sveltos.projectsveltos.io/k8sCleaner.html and click the "Getting Started" button to try K8s-cleaner.

Key Features:

- Easy to Use: No complex setup or configuration required—perfect for developers and operators alike - Open Source: Modify the code to better fit your specific needs - Community Driven: We welcome your feedback, feature ideas, and bug reports to help improve K8s-cleaner for everyone

I'm here to answer questions, address feedback, and discuss ideas for future improvements.

Looking forward to your thoughts! And make sure your all you kubernetes clusters are sparkling clean for the holidays. :-)

Simone

Show HN: K8s Cleaner – Roomba for Kubernetes
sveltos.projectsveltos.io

Re: Show HN: K8s Cleaner – Roomba for Kubernetes

#4
When I saw the headline I was pretty excited, but looking at your examples, I'm really curious about why you decided to make everything work via CRDs? Also having to write code inside those CRD for the cleanup logic seems like a pretty steep learning curve and honestly I'd be pretty scared to end up writing something that would delete my entire cluster.

Any reason why you chose this approach over something like a CLI tool you can run on your cluster?

Re: Show HN: K8s Cleaner – Roomba for Kubernetes

#6
post #4

When I saw the headline I was pretty excited, but looking at your examples, I'm really curious about why you decided to make everything work via CRDs? Also having to write code inside those CRD for the cleanup logic seems like a pretty steep learning curve and honestly I'd be pretty scared to end up writing something that would delete my entire cluster. Any reason why you chose this approach over something like a CLI…

It has a DryRun that generates a report on which resources would be affected. So you can see what resources identifies as unused before asking it to remove those. I would be scared as well otherwise. Agree.
Post reply on HN