<p>I have an OpenShift BuildConfig that creates a Docker image stored in a remote repository. The DeploymentConfig uses an OpenShift ImageStream to trigger a deployment when a new image is available. I've managed to push to the remote repo and sync the ImageStream from the remote repo. However, when I run a fresh build, the ImageStream does not automatically sync up with the remote repo. New deployments use the old image until that occurs. I have found that I can not have multiple <code>spec.output.to</code> fields in the BuildConfig or I'd just push it to both locations. I have set the <code>importPolicy.scheduled: true</code> field, but by default this only imports every 15 minutes and at that point the deployment trigger fires and the new version is deployed. I'd like to not wait for that time. I'd prefer not to make a global config change for this. I'd be willing to push to the local docker repo and push that to the external if there is a way to accomplish this.</p>

<p>How can I be sure at build time that the ImageStream is sync'd so a deployment is triggered? </p>

Josiah
<p>How about try to adjust <a href="https://docs.openshift.com/container-platform/3.11/install_config/master_node_configuration.html#master-config-image-policy-config" rel="nofollow noreferrer">Image Policy Configuration
</a> in <code>/etc/origin/master/master-config.yaml</code> ? 
This post is also helpful for your case, refer <a href="https://blog.openshift.com/automatically-update-red-hat-container-images-on-openshift-3-11/" rel="nofollow noreferrer">Automatically Update Red Hat Container Images on OpenShift 3.11</a> for more details. </p>

<p>Or when you images are pushed by CI/CD, you can consider to configure post trigger to execute <code>oc import-image &lt;imagestream name&gt;:&lt;tag&gt; --confirm</code> for manual sync.</p>
