Keel looks nearly identical to what I’m looking for. I can’t quite recall how the functionality worked in what I watched, but I believe (one of the ways that) it worked was by creating a new git branch for each update. I see Keel has approval functionality, but I don’t see anything about git integration.
If you use Keel, do you just rely on Kubernetes deployment versions for update history and other tools for config backups?
Is this the Quadlet you mentioned? The repo states it was merged into Podman. It seems pretty similar to the podman-auto-update from the article.
I wasn’t aware of this functionality, but I don’t think it provides the functionality I’m looking for. I might have missed it in the documentation, but it doesn’t seem to look for new version tag updates.
For example, Forgejo’s image registry on Codeberg doesn’t have tags like latest
, stable
, etc. and instead just has semantic versions like 1.19.1
, 1.19.2
, 1.19.3
, 1.20.1
, etc. From what I’m seeing, the images wouldn’t auto update unless the tags that omit the bugfix version like 1.19
or 1.20
are used. However, Podman still wouldn’t update across those minor version updates.
I found what I was looking for - Renovate. I was wrong about it making branches (just makes pull requests). Looking into it a little further though, it seems people use Renovate (to automate updates) in conjunction with something like Argo (to automate deployments).
I think Keel does both of those tasks? I still need to research the similarities/differences of Keel and Renovate a bit further. Thanks again for the recommendation!