> On 18 Apr 2023, at 16:15, Johannes Kastl <email@example.com> wrote:
> Hi all,
> I am in the process of rewriting my helm chart for 389ds (stay tuned, I'll send another mail once it is ready), and noticed the lack of recent tags for the container images:
> https://hub.docker.com/r/389ds/dirsrv only has 2.1, 2.2 and latest. 2.2 and latest are 8 months old.
The docker.com images are maintained by myself at SUSE. Because of how we build them from https://build.opensuse.org/ and via https://registry.opensuse.org/ we can't actually "patch" 2.2 and 2.1, so we really only have latest. Hindsight is perfect I guess ....
I've also been really busy lately with other projects which probably hasn't helped me keep things "up to date" as they should be either.
If one of the others from the 389 team wanted I'm happy to give them admin on the hub.docker.com 389ds project so they can assist :)
> https://quay.io/repository/389ds/dirsrv?tab=tags only has latest and c9s without any version tags (or I did not find them?).
> Would it be possible to publish the tags more often? And maybe publish all patch versions (2.2.1, 2.2.6, ...) in addition?
> Using "latest" or "stable" is not a good idea for container workloads, as it does not allow rollbacks in case of errors or changed behaviour. Rolling back is easy using helm charts, but only if the image can be changed back from say 2.2.6 to 2.2.5 by helm. When using stable or 2.2 or similar, the new image will be fetched and the old one discarded, so it will be lost and no longer usable.
> Having usable tags would really be helpful, so I would be happy if this could be done.
The challenge is building everything in that way.
As well, worth pointing out that 389-ds does not support *downgrades*. only upgrades. So downpatching may/may not always work.
Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia
389-users mailing list -- firstname.lastname@example.org
To unsubscribe send an email to email@example.com
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://firstname.lastname@example.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Post a Comment