Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: K8s Cleaner – Roomba for Kubernetes

sveltos.projectsveltos.io

Post reply on HN
Print view View original

11–20 of 64 posts

Re: Show HN: K8s Cleaner – Roomba for Kubernetes

#11

Post by mgianluc »

S0y wrote: 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…

one more thing. It comes with a huge library of use cases already covered. So you don't necessarily need to write any new instance.

You would need to do that only if you have your own proprietary CRDs or some use case that is not already covered.

Re: Show HN: K8s Cleaner – Roomba for Kubernetes

#12

Post by pescerosso »

devops99 wrote: post #3

If you find yourself using something like this, you seriously fucked up as DevOps / cloud admin / whatever.

I understand where you’re coming from, and ideally, we strive for well-managed Kubernetes environments. However, as DevOps practitioners, we often face complexities that lead to stale or orphaned resources due to fast deployment cycles, changing application needs or teams. Even the public clouds make lots of money from services that are left running and not used for which some companies make a living helping clean things up.

K8s-cleaner serves as a helpful safety net to automate the identification and cleanup of these resources, reducing manual overhead and minimizing human error. It allows teams to focus on strategic tasks instead of day-to-day resource management.

Re: Show HN: K8s Cleaner – Roomba for Kubernetes

#15

Post by mgianluc »

darkwater wrote: post #14

How does it work in an IaC/CD scenario, with things like Terraform or ArgoCD creating and syncing resources lifecycle inside the cluster? A stale resource, as identified and cleaned by K8s Cleaner, would be recreated in the next sync cycle, right?

In that case I would use it in DryRun mode and have it generate a report. Then look at the report and if it makes sense, fix the terraform or ArgoCD configuration.

More on report: https://gianlucam76.github.io/k8s-cleaner/reports/k8s-cleane...

Re: Show HN: K8s Cleaner – Roomba for Kubernetes

#16

Post by sethhochberg »

empath75 wrote: post #2

why isn't this just a cli tool? I don't see any reason it needs to be installed on a cluster. There should at least be an option to scan a cluster from the cli.

Ironically, I'd bet environments most desperately in need of tools like this are some of the ones where there has been lots of "just run this Helm chart/manifest!" admining over the years...

Re: Show HN: K8s Cleaner – Roomba for Kubernetes

#18

Post by devops99 »

pescerosso wrote: post #12
devops99 wrote: post #3

If you find yourself using something like this, you seriously fucked up as DevOps / cloud admin / whatever.

I understand where you’re coming from, and ideally, we strive for well-managed Kubernetes environments. However, as DevOps practitioners, we often face complexities that lead to stale or orphaned resources due to fast deployment cycles, changing application needs or teams. Even the public clouds make lots of money from services that are left running and not used for which some companies make a living helping clean th…

> However, as DevOps practitioners, we often face complexities that lead to stale or orphaned resources due to fast deployment cycles

So, as a DevOps practitioner myself, I had enough say within the organizations I worked at, who are now clients, and also my other clients, that anything not in a dev environment goes through our GitOps pipeline. Other than the GitOps pipeline, there is zero write access to anything not dev.

If we stop using a resource, we remove a line or two (usually just one) in a manifest file, the GitOps pipeline takes care of the rest.

Not a single thing is unaccounted for, even if indirectly.

That said, the DevOps-in-name-only clowns far outnumber actual DevOps people, and there is no doubt a large market for your product.

edited: added clarity

Re: Show HN: K8s Cleaner – Roomba for Kubernetes

#19

Post by paolop »

I've been using it for a bit now and very happy with it. The stale-persistent-volume-claim detection has been almost a 100% hit in my case; it's a real game-changer for cleaning up disk space.

Kubernetes clutter can quickly become a headache, and having a tool like this to identify and remove unused resources has made my workflow so much smoother.

Re: Show HN: K8s Cleaner – Roomba for Kubernetes

#20

Post by resouer »

S0y wrote: 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…

A CRD controller is expected, especially it will allow your clean up logic long running in cluster or periodically. But writing code inside YAML is very weird, at least there are CEL as option here.
Post reply on HN