CHAPTER 3. DEPLOYMENTS WARNING Config change deployment triggers NOTE Config change deployment trigger Image change deployment triggers Image change deployment trigger With the above example, when the  latest  tag value of the  origin-ruby-sample  image stream changes and the new image value differs from the current image specified in the  DeploymentConfig  object’s  helloworld  container, a new replication controller is created using the new image for the  helloworld container. The image change trigger results in a new replication controller whenever the content of an image stream tag changes (when a new version of the image is pushed). triggers: - type:  "ConfigChange" If a config change trigger is defined on a  DeploymentConfig  object, the first replication controller is automatically created soon after the   object itself is created and it is not paused. The config change trigger results in a new replication controller whenever configuration changes are detected in the pod template of the  DeploymentConfig  object. If no triggers are defined on a  DeploymentConfig  object, a config change trigger is added by default. If triggers are defined as an empty field, deployments must be started manually. triggers: - type:  "ImageChange" imageChangeParams: automatic:  true 1 from: kind:  "ImageStreamTag" name:  "origin-ruby-sample:latest" namespace:  "myproject" containerNames: -  "helloworld" 1 If the  imageChangeParams.automatic  field is set to  false , the trigger is disabled. 53