k8s-cleaner VS shell-operator

As Kubernetes deployments grow in complexity and scale, maintaining a clean and efficient cluster becomes increasingly important. While Kubernetes provides tools for resource management, such as garbage collection, it can still be challenging to identify and remove unused or stale resources manually. This is where k8s-cleaner comes in.

So I created a Cleaner: https://github.com/gianlucam76/k8s-cleaner controller to automate the removal of stale Kubernetes resources.

Maybe, the Shell operator is a good tool for that?

Shell-operator to parse logs and make action after the pod crash.

Argo workflow can trigger from k8s objects but may be a bit more than you need, shell-operator may be good enough https://github.com/flant/shell-operator for a quick win

I used https://github.com/flant/shell-operator to write a simple Kubernetes operator that automatically creates subdomains for your services by patching an existing ingress.

If you are more into lightweight and common use cases, look at metacontroller or the shell-operator.

Believe it or not, you can write a Kubernetes operator using simple shell scripts: https://github.com/flant/shell-operator

You could use something like shell operator, metacontroller, or operator-sdk to run a command against your load balancer's API whenever a LoadBalancer service is created.

https://github.com/flant/shell-operator should get you quite far but this sounds like the process should just shut itself down when that case is hit...

shell-operator is already used in KubeSphere's ks-installer, Confluent's Kafka DevOps solution, Deckhouse Kubernetes platform, and more. All documentation is available in the project's GitHub repo — if you feel it might be interesting for your needs, give it a try! Any feedback is warmly welcome.