alt Hacker NewsShow HN: Renovate – The Kubernetes-Native Way
Hey folks, we built a Kubernetes operator for Renovate and wanted to share it. Instead of running Renovate as a cron job or relying on hosted services, this operator lets you manage it as a native Kubernetes resource with CRDs. You define your repos and config declaratively, and the operator handles scheduling and execution inside your cluster. No external dependencies, no SaaS lock-in, no webhook setup. The whole thing is open source and will stay that way – there's no paid tier or monetization plan behind it, we just needed this ourselves and figured others might too.
Would love to hear feedback or ideas if you give it a try: https://github.com/mogenius/renovate-operator
Comments
I’m curious to know why this requires a whole CRD + operator setup, instead of just being a deployment that watches config(s) somewhere?
I'm struggling to see how this operator helps-- is there some scenario that I cannot imagine that others are dealing with where this operator is useful? Specifically, what problems does this solve?
news.ycombinator.com/item?id=43677067
[dead]
[flagged]
So that's an in-cluster supply chain attack enabler? :)
It is nice to see more work on renovate but your comparison, especially the points on filtering, license keys and discovery, seems misleading for at least GitLab.
Both work with mend's renovate WITHOUT a license key, see also https://gitlab.com/renovate-bot/renovate-runner. As it is just a scheduled pipeline then you can also adjust frequency, timeouts and more.