Don’t let these naysayers here discourage you. I’ve used CCleaner on Windows 20 years ago, so why not finally now on my kube cluster.
Show HN: K8s Cleaner – Roomba for Kubernetes
31–40 of 64 posts
Re: Show HN: K8s Cleaner – Roomba for Kubernetes
#32If you find yourself using something like this, you seriously fucked up as DevOps / cloud admin / whatever.
Not all third party Kubernetes controllers are created equal, unfortunately.
And it is also the reality that not every infra team gets final say on what operators we have to deploy to our clusters (yet we're stuck cleaning up the messes they leave behind).
Re: Show HN: K8s Cleaner – Roomba for Kubernetes
#33Earlier quoted context omitted.
> 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 no…
A tool that would be useful for organizations that don't have superstar, ultra-competent devops people on the full-time payroll sounds pretty useful in general. There are a lot of companies that just aren't at the scale to justify hiring someone for that kind of role, and even then, it's hard to find really good people who know what they are doing.
[deleted]
Re: Show HN: K8s Cleaner – Roomba for Kubernetes
#34If you find yourself using something like this, you seriously fucked up as DevOps / cloud admin / whatever.
I don't agree, you can see it as just another linting tool. Just like your IDE will warn of unused variables and functions, and offer a quick-fix to remove them. You wouldn't call someone a fucked up programmer for using an IDE.
Re: Show HN: K8s Cleaner – Roomba for Kubernetes
#35If you find yourself using something like this, you seriously fucked up as DevOps / cloud admin / whatever.
Or you're budget constrained, and haven't yet been able to allocate resources to things like GitOps.
Re: Show HN: K8s Cleaner – Roomba for Kubernetes
#36If you find yourself using something like this, you seriously fucked up as DevOps / cloud admin / whatever.
I don't agree, you can see it as just another linting tool. Just like your IDE will warn of unused variables and functions, and offer a quick-fix to remove them. You wouldn't call someone a fucked up programmer for using an IDE.
[flagged]
Re: Show HN: K8s Cleaner – Roomba for Kubernetes
#37I feel like the fact that this even needs to exist is a damning indictment of k8s.
Oh, good to know that your environment never loses track of any cloud resource. Maybe apply to Netflix, since it seems they're still trying to solve that problem https://www.theregister.com/2024/12/18/netflix_aws_managemen... https://news.ycombinator.com/item?id=42448541>
Re: Show HN: K8s Cleaner – Roomba for Kubernetes
#38I've been saying for a while that most of the time we didn't replace pets with cattle bit pet servers with pet clusters.
The need for a tool like this proves my point
Re: Show HN: K8s Cleaner – Roomba for Kubernetes
#39Earlier quoted context omitted.
I don't agree, you can see it as just another linting tool. Just like your IDE will warn of unused variables and functions, and offer a quick-fix to remove them. You wouldn't call someone a fucked up programmer for using an IDE.
[flagged]
I am assuming that the tool provides a list and asks for confirmation before deleting? Does it just go and automatically delete stuff in the background at any time?
edit: yes I see a "dry run" option, which is how I would use it. I also see a "scheduled" option which is probably what you're criticizing. Hard to tell, you're quicker with the insulting than the arguing.
Re: Show HN: K8s Cleaner – Roomba for Kubernetes
#40Earlier quoted context omitted.
Or the person working that role before you did and you are trying to manage the situation as best as possible.
As a cloud/DevOps consultant, I don't believe in letting management drag on the life support of failed deployments. We (the team I built out since a couple years ago) carve out a new AWS subaccount / GCP Project or bare-metal K8s or whatever the environment is, instantiate our GitOps pipeline, and services get cut-over in order to get supported. When I was working in individual contributor roles, I managed to "manage…
It's really hard to parse what you are trying to say in the middle of this colorful imagery and quotations, but if you are spinning up a new Kubernetes cluster (and AWS/GCP account) per deployment, it's obvious you don't need this tool.