New answers tagged

0

The most stable way to assure you're deploying a consistent image is to use the digest instead of tags. The digest is like the git sha of a container image. This assures that if someone uploads a new image and tags it with an existing version tag, either accidentally or maliciously, you will continue to pull the known good image. The drawback is digests are ...


2

First a couple key points: Tags are mutable in most registries, so v1 today may be different from v1 a month ago. However clients do need to pull this tag again to see the updates. Multiple tags may point to the same image. So stable and v1 could point to the same image. Pointing to a digest ensures the image is immutable, however you will not receive ...


1

While I generally do not recommend GitFlow these days, fully automated way to do what you ask is possible to achieve with an external system. Below I will describe how to do it with Reliza Hub (which is the one I'm developing - but you may find other options). Here is the idea - You create your project in Reliza Hub and choose versioning schema, i.e. semver....


Top 50 recent answers are included