Remote container tag in k8s deployments is not unique #839

New Issue

dboreham · 2024-06-13T12:31:37Z

dboreham commented

2024-06-13 12:31:37 +00:00

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.

dboreham self-assigned this 2024-06-13 12:31:37 +00:00

dboreham commented

2024-06-13 12:32:04 +00:00

Fixed in : #838

Fixed in : https://git.vdb.to/cerc-io/stack-orchestrator/pulls/838

dboreham closed this issue

2024-06-13 12:32:04 +00:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#839