In this lesson, you will learn how to implement Semantic Versioning (SemVer) within your Docker workflow to create predictable deployment paths and reliable rollback triggers.
Why Tags Matter
Up until now, you’ve likely relied on the latest tag when building your images. While convenient for local development, latest is a "moving target." In a production environment, if a deployment fails, you need to know exactly which version of your code was running before the update. Semantic Versioning provides a standardized format—MAJOR.MINOR.PATCH—to communicate the nature of changes in your image:
- MAJOR: Incompatible API changes.
- MINOR: New functionality added in a backward-compatible manner.
- PATCH: Backward-compatible bug fixes.
Implementing the Strategy
When building your images, never rely solely on a single tag. Instead, apply multiple tags to a single build artifact during your CI process. This allows your Kubernetes manifests to point to a specific, immutable version while still allowing automated tools to track updates.
For example, if you are releasing a bug fix for version 1.2.0, your build process should tag the image with both the specific version and the general minor release:
# Tagging with the specific patch version
docker build -t my-app:1.2.1 .
# Tagging with the minor version for rolling updates
docker tag my-app:1.2.1 my-app:1.2
# Push both to your registry
docker push my-app:1.2.1
docker push my-app:1.2
Facilitating Rollbacks
By using SemVer, your Kubernetes deployment manifests become self-documenting. If my-app:1.2.1 introduces a regression, your rollback strategy is as simple as updating your manifest to point back to my-app:1.2.0. Because these tags are immutable—meaning you never overwrite the contents of 1.2.0 once it is pushed—you can guarantee that rolling back will restore your environment to its exact previous state without unexpected "latest" side effects.
This strategy removes the guesswork from your CI/CD pipeline, ensuring that every deployment is traceable, debuggable, and safe.
Key Takeaway: Use Semantic Versioning tags for every production image to ensure that your deployments are immutable, traceable, and easily reversible.