You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when we push images for testing for PRs they are tagged as pr-<pr-no.> eg: pr-120 where 120 is the number of the PR.
However, we do not tag the image with the required version when releasing or pushing to production. We just push the image with the latest tag and then deploy to production.
Tagging images during release will allow developers to find the images and test them more easily.
Using explicit tags for helm releases are also important for ease of debugging, reproducibility and reducing ambiguity during deployment.
The text was updated successfully, but these errors were encountered:
Currently when we push images for testing for PRs they are tagged as pr-<pr-no.> eg: pr-120 where 120 is the number of the PR.
However, we do not tag the image with the required version when releasing or pushing to production. We just push the image with the latest tag and then deploy to production.
Tagging images during release will allow developers to find the images and test them more easily.
Using explicit tags for helm releases are also important for ease of debugging, reproducibility and reducing ambiguity during deployment.
The text was updated successfully, but these errors were encountered: