Are you asking if the router will send traffic to a back-end before the readiness probes succeed? If so, no. The router looks at the service endpoints (you can see them with 'oc get endpoints'). Until a pod passes readiness checks it will not be added to the endpoints, so the haproxy never sees the back-end in the configuration.
-ben On Mon, Aug 1, 2016 at 11:47 PM, Srinivas Naga Kotaru (skotaru) < [email protected]> wrote: > Actual router haproxy config. During rolling code deployment scenarios, > container might wait till it finish readiness probe successful. However, > HAProxy router might start send traffic since it TCP simple probe was > successful? Service mightn’t be fully up except process just started? > > > -- > *Srinivas Kotaru* > > From: "[email protected]" <[email protected]> > Date: Monday, August 1, 2016 at 8:30 PM > To: skotaru <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: routers probes Vs container probes > > When you say router config, are you referring to the deployment config for > the router, or the actually haproxy config file itself? > > On Aug 1, 2016, at 1:44 PM, Srinivas Naga Kotaru (skotaru) < > [email protected]> wrote: > > Have few questions on how router probes works with in conjunction with > container live & readiness probes? Just looking at router config, it was > configured with basic tcp probes but not http. How rolling restart scenario > works with relation router probes vs container probes? > > -- > *Srinivas Kotaru* > > _______________________________________________ > 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 > >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
