[HN Gopher] Show HN: Renovate - The Kubernetes-Native Way
       ___________________________________________________________________
        
       Show 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
        
       Author : JanLepsky
       Score  : 37 points
       Date   : 2026-02-11 14:36 UTC (8 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | andix wrote:
       | So that's an in-cluster supply chain attack enabler? :)
        
       | rirze wrote:
       | 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?
        
         | baby_souffle wrote:
         | Renovate lets you configure most things in each repos
         | individual config file.
         | 
         | I can only imagine a set of intersecting edge cases where
         | operator pattern is the most logical solution...
         | 
         | Edit: good answers here.
         | https://old.reddit.com/r/kubernetes/comments/1r1u7um/renovat...
        
           | rirze wrote:
           | So... helm without helm?
        
         | JanLepsky wrote:
         | There's several benefits we had in mind when building this
         | (after using self-hosted Renovate ourselves): k8s-native
         | approach: It uses CRDs, so that Renovate configs are Kubernetes
         | resources. You can manage them more easily/granular with
         | Argo/Flux/kubectl as part of existing workflows instead of a
         | Cronjob. Job isolation: The operator spawns individual jobs per
         | repo instead of one run. If a repo is stuck it doesn't block
         | everything else. Webhook support: repos get updated
         | immediately, not just on the next cron cycle. Visibility:
         | There's a light-weight, built-in UI showing repos, job status,
         | and progress.
         | 
         | There's more on the Github repo, we added a full list of
         | features and benefits to the readme.
         | 
         | Of course, in the end it comes down to individual preferences
         | :) Not saying one way is better than the other. We just felt
         | that for us, the operator-based approach would work better and
         | we're happy if the project is benefitial for others as well!
        
           | bryanlarsen wrote:
           | Can you step back further and explain what Renovate and its
           | competitors like Mend actually do, and what kind of tasks
           | people use them for?
        
             | JanLepsky wrote:
             | In short, Renovate (by Mend) is a dependency manager for
             | software projects. It watches your repository for outdated
             | libraries, packages, and frameworks and opens Pull Requests
             | to update them.
        
             | maverwa wrote:
             | Mend is not a competitor, renovate is the software, mend is
             | the company.
             | 
             | They are tools that automatically check your repo for
             | dependencies and create PRs when there are updates. It
             | supports a wide range of package managers and other places
             | dependencies may be specified.
             | 
             | Dependabot is another solution which is more ,,GitHub-
             | native" maybe.
        
             | esafak wrote:
             | To help you automate dependency updates, similar to
             | dependabot.
             | 
             | https://www.mend.io/renovate/
             | 
             | https://github.blog/news-insights/product-news/keep-all-
             | your...
        
             | jamietanna wrote:
             | See also: https://news.ycombinator.com/item?id=40011111
             | 
             | (a blog post I wrote, prior to joining Mend and working as
             | a Renovate maintainer)
        
       | Amol-917 wrote:
       | news.ycombinator.com/item?id=43677067
        
       | c0balt wrote:
       | 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.
        
         | jamietanna wrote:
         | I think the confusion is also because it's a comparison of
         | Community Self-Hosted (CE) vs the pure Open Source CLI - the
         | latter is what works without license key
         | 
         | I'll see if I can help with clarifying this in the table!
         | 
         | (I'm a Renovate maintainer and employee at Mend)
        
       | FridgeSeal wrote:
       | I'm curious to know why this requires a whole CRD + operator
       | setup, instead of just being a deployment that watches config(s)
       | somewhere?
        
         | zufallsheld wrote:
         | Presumably a CR can be validated by k8s against a schema and
         | will fail at an early step. I admit I like the operator-
         | pattern.
        
       ___________________________________________________________________
       (page generated 2026-02-11 23:01 UTC)