Think about image / chart pinning strategy #78

Open
opened 2025-05-29 20:12:52 +00:00 by GhostPLACEHOLDER · 2 comments

We need to this about it, if we don't pin them, then we probably never get updates.

So we should pin the images and charts a little more. Renovate has a handy versioning for the bitnami docker images.

We need to this about it, if we don't pin them, then we probably never get updates. So we should pin the images and charts a little more. Renovate has a handy versioning for the bitnami docker images.

Sample:

72318e1d4a/flux/apps/charts/backup/templates/backup.yaml (L17)

This will pull the image once and never again. So we never tet updates.

https://github.com/instrumentisto/rsync-ssh-docker-image/blob/main/CHANGELOG.md

That image needs addional renovaste config, so renovate understands the versioning (default docker versioning doesn't support prefixes by default).

Sample: https://code.forgejo.org/infrastructure/k8s-cluster/src/commit/72318e1d4abab95db5aa14fb44d95389e18c7e21/flux/apps/charts/backup/templates/backup.yaml#L17 This will pull the image once and never again. So we never tet updates. https://github.com/instrumentisto/rsync-ssh-docker-image/blob/main/CHANGELOG.md That image needs addional renovaste config, so renovate understands the versioning (default docker versioning doesn't support prefixes by default).
- #231
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/k8s-cluster#78
No description provided.