Okay thanks. We're now pushing to our openshift registry. Now we're able to automate the deploy of our new images. But te images will always have the tag :latest. Isn't there a better way to automate the deploy but still see which version of image we're using?
From: [email protected] Date: Fri, 4 Mar 2016 12:15:07 -0500 Subject: Re: image stream on image of private registry To: [email protected] CC: [email protected] Imported images from an external registry must be scheduled for import if you want to pick up changes. Use --scheduled on oc tag if you want that. Images are checked every 15 minutes by default. We generally don't recommend using an external registry if you are trying to do fast iteration. Push to the integrated registry - it's why it exists. On Mar 4, 2016, at 10:28 AM, Lorenz Vanthillo <[email protected]> wrote: We have an openshift origin 1.1.3 cluster. When we push an image to a registry we can import the image by oc import-image.. after that we create a new image stream and use the imageref of the image stream which is created after the oc import. So we only need to perform a new tag when we try to deploy a container with a new image. But now we want some fast test environment to deploy. We create an image with the tag :latest and push it to the registry. When we create a new image we use the -f flag to overwrite the tag. So we're always pushing the same image with the same tag. we've performed an oc import on that image:latest. But after pushing a new image the old remains deployed. What can we do to trigger an automatic deployment when there is a new image in the repository? _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
