Hi Johannes,
On Tue, Apr 18, 2023 at 8:15 AM Johannes Kastl <ka...@b1-systems.de> 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: > Oh, nice! Looking forward to it! > > https://hub.docker.com/r/389ds/dirsrv only has 2.1, 2.2 and latest. 2.2 > and > latest are 8 months old. > > 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? > Yes, it's possible. 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. > Yes, that's understandable. As you already found out, we have a split brain situation with images in different registries, so I wanted to sort this out first. But I can tags to quay.io repos. One thing to keep in mind though: those minor releases might be less tested. I chose to follow packages in Fedora rather than 389-ds-base versions because these packages go through testing with FreeIPA and OpenQA. But I guess with helm and deployments rollback this is less of an issue. Thanks. > > Having usable tags would really be helpful, so I would be happy if this > could be > done. > > Have a nice day, everyone! > > Kind Regards, > Johannes > > -- > Johannes Kastl > Linux Consultant & Trainer > Tel.: +49 (0) 151 2372 5802 > Mail: ka...@b1-systems.de > > B1 Systems GmbH > Osterfeldstraße 7 / 85088 Vohburg > http://www.b1-systems.de > GF: Ralph Dehner > Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 > _______________________________________________ > 389-users mailing list -- 389-users@lists.fedoraproject.org > To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org > 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://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Viktor
_______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org 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://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
