We generate a "remote" tag for each SO-supplied container in a k8s deployment.
Unfortunately the tag is only unique as far as its name.
This means that multiple concurrent deployments of the same stack, for example, will get the same image tags.
The behavior would be wrong and definitely confusing because the last pushed image would be used on any pull event.
It makes deploying a staging and production stack side by side problematic.
Resolve by mixing in some entropy from the deployment id into the remote image tag names.
We generate a "remote" tag for each SO-supplied container in a k8s deployment. Unfortunately the tag is only unique as far as its name. This means that multiple concurrent deployments of the same stack, for example, will get the same image tags. The behavior would be wrong and definitely confusing because the last pushed image would be used on any pull event. It makes deploying a staging and production stack side by side problematic.
Resolve by mixing in some entropy from the deployment id into the remote image tag names.