Renovate: The Kubernetes-Native Way
Run Renovate on your own infrastructure with CRD-based scheduling, parallel execution, auto-discovery, and a built-in UI. If you self-host Renovate and already run Kubernetes, this operator gives you the control and observability that plain self-hosted setups lack.
Comparison with Mend Renovate CE
Feature Mend Renovate CE Renovate Operator Fully open source, no signup or license key ❌ ✅ Automated dependency updates ✅ ✅ Runs on your own infrastructure ✅ ✅ Auto-discovery ✅ ✅ Webhook API for on-demand runs ✅ ✅ Web UI ✅ ✅ Declarative cron scheduling via CRD ❌ ✅ Auto-discovery with group/topic filtering ❌ ✅ Per-project status tracking in-cluster ❌ ✅ Parallel execution with concurrency control ❌ ✅ Prometheus metrics & health checks ❌ ✅ Kubernetes-native pod scheduling ❌ ✅ Leader election for high availability ❌ ✅ Job lifecycle management (TTL, deadlines, retries) ❌ ✅
How it works
At the defined time of your schedule, a renovate discovery job is started After the discovery finished, you will be able to see all your discovered projects in the UI All projects are now being set to be scheduled Every 10 seconds the operator checks for schedules projects and starts a new renovate job Only as many jobs as defined in spec.parallelism are getting executed at the same time
Installation
Helm
Option 1: OCI Registry
helm -n renovate-operator upgrade --install renovate-operator \ oci://ghcr.io/mogenius/helm-charts/renovate-operator \ --create-namespace --wait
... continue reading