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.
show comments
FridgeSeal
I’m curious to know why this requires a whole CRD + operator setup, instead of just being a deployment that watches config(s) somewhere?
show comments
rirze
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?
show comments
Amol-917
news.ycombinator.com/item?id=43677067
andix
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.
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
So that's an in-cluster supply chain attack enabler? :)