bjartek · August 14, 2017 23:40 · jorgemoralespou · Aug 14, 2017
diff --git a/gistfile1.txt b/gistfile1.txt
 Lets say you have a DeploymentConfig that is running two containers. 
 - a nginx container with static content
 - a nodejs container

 Both of these containers are deployed with the same version. 

 How do you ensure that they are always delpoyed with the same version?

 If you use ImageChangeTriggers on both of them then will there not be a small time where one of them can run another version then the other?

 Any alternate way of doing this? What we have though about is:
 - seperate the versioning of the two parts of the application. However for us this does not feel natural. The application is developed as a whole, and splitting up the slim backend-for-frontend and the frontend itself is not nautral
 - create a container with both nginx and nodejs/express in it. Not a good solution either since we have to maintain baseimage and it does not "feel" right.
	Lets say you have a DeploymentConfig that is running two containers.
	- a nginx container with static content
	- a nodejs container

	Both of these containers are deployed with the same version.

	How do you ensure that they are always delpoyed with the same version?

	If you use ImageChangeTriggers on both of them then will there not be a small time where one of them can run another version then the other?

	Any alternate way of doing this? What we have though about is:
	- seperate the versioning of the two parts of the application. However for us this does not feel natural. The application is developed as a whole, and splitting up the slim backend-for-frontend and the frontend itself is not nautral
	- create a container with both nginx and nodejs/express in it. Not a good solution either since we have to maintain baseimage and it does not "feel" right.