I am currently switching from docker compose to kubernetes. Along with that, I am changing from using the :latest tag on everything to explicit versions.

Now, it’s a lot of work to check all the GitHub pages for the releases and updating.

Is there some kind of dashboard that ideally would show me (per app) the version I am running vs. the current version from GitHub? (With a link to the release notes, while we are at it…).

Or is my workflow wrong to begin with? (Haven’t looked too deep into something like argocd, maybe that’s the answer?)

  • dfense@lemmy.worldOPEnglish
    5·
    8 hours ago

    Wow, thanks for all the great answers so far. As for why not latest:

    1. Read a lot online and read multiple times it’s “bad practice”
    2. Own experience: had latest on an app which crashed and wouldn’t come up again. Got the backup of the persistent volume back and then had the problem that latest at that point is not the same as latest when I spun it up. Actually had no idea which version I was running last and consequently what I would need to pull to fit my backup. In case I have to restore my cluster, this problem is multiplied.
    3. I run NixOS on everything, so I am clearly biased towards reproducibility.
    4. I am running Services for family and a fire brigade (nothing mission critical, just support stuff, but still…). Stability is important, as sometimes I do not have the time to immediately react to an issue. I prefer a lazy Sunday morning to update/fix and then leave it alone and stable.

    So, probably a combination of latest for low criticality and pinned on critical stuff (e.g. authentication, access, etc.)

    • i_am_not_a_robot@discuss.tchncs.deEnglish
      2·
      4 hours ago

      It is bad practice because of point 2 and if you have multiple replicas you can probably get different versions running simultaneously (never tried it). Get Rennovate. It creates PRs to increment the version number and it tries to give you the release notes right in the PR.