Dependency Updates and further development

[Breee]

Hey man,

do you plan to setup automatic dependency updates for your project?

I'm very interested in this and would love to collaborate

or did you find a better solution than this operator?

[secustor]

If it is actually used I can look into this in the future.

Back then I have wrote this mainly for self teaching the operator sdk.

Now, I mostly use CI systems or my Backstage plugins for running it.

https://github.com/secustor/backstage-plugins/tree/main

[Breee]

I see. I'll take a look on your backstage plugins, that sounds awesome.

Else yes, i'm interested in using it and probably also more people.
I'm facing the challenge to renovate multiple thousand repositories on our selfhosted gitlab.
Currently we do it with some selfwritten tool that fills up a redis queue and a celery worker processes it by spawing renovate containers.

Using a k8s operator would be much more appealing for me, that's why my next steps would be to write an operator

I'm interested in contributing, if you can help me getting started to get a dev instance running.

[secustor]

Basically there are 3 components.

• the operator
• the shipper
• and renovate jobs

the operator triggers "Runs" and the general configurations. This Runs are jobs which run the shipper. The shipper in turn runs the discovery for Renovate to create a list of targets to run Renovate against. Based on that list the shipper generates a an indexed Kubernetes job to run Renovate in batches.

So you need to run ensure that the Shipper image is available in the cluster, but the operator can also be run outside

To run the operator:

renovate-operator/Makefile

Line 101 in ecaab16

run: manifests generate fmt vet ## Run a controller from your host.

To build the shipper:

renovate-operator/Makefile

Line 210 in ecaab16

shipper-docker-build: