Every time you run a rolling deployment in OpenShift, a canary check runs by default: https://github.com/openshift/origin/blob/master/examples/deployment/README.md#rolling-deployments-with-canary-checks
In the future, we will (probably) natively support AB deployments: you will be able to specify a percentage of the new pods you want to run alongside your old pods w/o having to run two different deployment configs and mess with selectors. On Thu, Aug 18, 2016 at 2:18 PM, Skarbek, John <[email protected]> wrote: > I don’t believe Openshift themselves have documentation covering this > deployment method, however, kubernetes certainly does. > > http://kubernetes.io/docs/user-guide/managing-deployments/#canary- > deployments > > Selectors are a key component to enabling this functionality. > > > > -- > John Skarbek > > On August 18, 2016 at 07:51:26, Ronan O Keeffe ([email protected]) > wrote: > > Hi, > > Just wondering is it possible via OpenShift for us to do a canary release > of an application? e.g. we put a new version of a component live alongside > the old version and push a only (tweakable) subset of traffic to the new > version? > > Ultimately I suppose we'd be running two different versions of the same > service simultaneously. > > oc v1.2.0 > kubernetes v1.2.0-36-g4a3f9c5 > > > Cheers, > Ronan. > > _______________________________________________ > users mailing list > [email protected] > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists. > openshift.redhat.com_openshiftmm_listinfo_users&d=DQICAg&c=_ > hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_ > M0oNfzEXXNp-tpx74&m=hIZdaBW9CLn6vZGCN84Olnq6SVQxuxXI5oFVSMQiwcU&s= > u1RekRVkzHlHLii-Y36bg50Lf0A-BYmekIp4AOayngI&e= > > > _______________________________________________ > 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
