3 ms·
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 havi
by S0y 2y ago
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?
- mgianluc 2y agoIt 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.
- mgianluc 2y agoone 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.
- resouer 2y agoA 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.