We are doing it WRONG! Containers deployment and promotion across environments

Optimizing Containers Continuous Deployment (CD) in a multi-environment scenario with Build Artifact, with an example in Azure Pipelines.

When you use containers for your application, one of the things you need to think about is how to move (aka promote) the container images you generate across different environments.

In this video I'm showing another, optimal way to promote containers images across environments, withouth the need of tight dependency between different container registries.

🆘 NEED HELP? 🆘
We can talk about GitHub, Azure DevOps, or any other DevOps tool or project you need help with!

🙏🏻SUPPORT THE CHANNEL🙏🏻

💬JOIN THE COMMUNITY

🎥VIDEOS

📄RESOURCES

❓QUESTIONS?
Have a question about DevOps, Cloud, Coding, or Anything Else? Post in comments section of this video!

_______________

🔮TOOLS I USE

📸🖥️GEAR AND SOFTWARE

Disclaimer:
Some product links are affiliate links which means if you buy something Il receive a small commission at no additional cost to you.
As an Amazon Associate, I earn from qualifying purchases.

[jobinjose]

Very nice explanation! BTW I have a question. Would it be possible to control the CD part based on branch used in CI phase? I need the CI to build image for all commits in all branches, but only the images from master branch to be promoted to UAT/Prod registry.

[jsmithdom]

Great video and so close to what I need. Any plans for an updated video with AKS implementation?

[jimstrawn]

Great presentation, Dave! I have been looking for exactly this explanation. The direction I was heading was to push the image to the Dev ACR, then from Dev to Test, Test to UAT, then UAT to Prod. And the reason I did that was to ensure nothing got sent to UAT that didn't first get sent to Test (etc.). But I suspect that's the wrong way to do that. Further, I ran into other problems because the first three environments are on different subscriptions than Prod, so crossing subscriptions is proving a challenge. However, all the stages have access to the artifacts! And it makes total sense to segregate the CI and the CD responsibilities. Thanks for this!

[ay]

Thank you! You did an excellent job explaining the CI and CD process. I like the new CD better.

[branimirkobescak]

it's ridiculous how difficult this was to find. I am in the process of setting up CI/CD for our docker projects and it made zero sense that every single guide/tutorial/documentation essentially did what you described at the beginning or even worse they literally did ALL of their deployments inside the build pipeline(CI). I knew this was wrong because I know that docker supports saving images as tar files which means we can just publish that tar file as an artifact for the release pipeline(s) to use and push on appropriate registries.

I almost went through the trouble of doing it all on my own from scratch but luckily I saw your blog mentioned in stackoverflow because google hasn't given me anything related to this.

[devopsengineer]

*Why no body asks real question .. how to change configuration like app settings.jason with respect to env like db connection string is different for all environment*

[rogernaranjo]

Wouldn't be possible to use now a container resource? We are "saving" the image already in the dev ACR

[margr]

Why do you push two images to ACR? (BuildId and Latest)

[nawazshaik]

Yaml file not found, plz share new link