Deployment Strategy?

[hafdev]

We are about to move to a new development and hosting environment (I am also new to Craft). Our planned development workflow is as follows: develop and test on a local craft cms docker container pointing to a local mysql container.

If all is fine, push changed files to remote GIT repo with a new tag: git tag. On our kubernetes cluster we have some automation in place, when a new tag is discovered a new craft cms image is built and copies our changed/add files, and from that a new container is started. This new craft cms container will become our new production container to replace the current production container that is customer facing.

However there will briefly be 2 craft cms containers pointing to one and the same production mysql db container. One (B) with a new version of craft cms or new templates and one (A) with an older version of craft cms or without the new templates.

Could this potentially cause problems with the database? Or how would this affect the current production container that is customer facing?

Any experiences or best-practices in such an environment?