In PCF we can set up the health check invocation timeout to execute X seconds after the instance has been created.  But before that, let's understand the PCF Health Check Lifecycle. Stage 1: The application is deployed to PCF Stage 2: When deploying the app, a health check type is specified and optionally a timeout. If a health check type is not specified, then the monitoring process defaults to a port health check Stage 3: Cloud Controller stages, starts, and runs the application Stage 4: Based on the type specified for the app, Cloud Controller configures a health check    that runs periodically for each app instance Stage 5: When Diego starts an app instance, the app health check runs every two seconds until a response indicates that the app instance is healthy or until the health check timeout elapses. The 2-seconds health check interval is not configurable Stage 6: When an app instance becomes healthy, its route is advertised, if applicable.    ...

BLUE GREEN DEPLOYMENT PCF Blue-Green deployment is a technique to reduce the downtime of applications during deployment and also reduce the risk ie. if something unexpected happens we have an option to roll back to the previous version by switching back There are two identical production environments running called Blue(live) and Green(idle) and at any time only one of the environments is live.  When a new version of the app/software needs to be deployed, final stage of testing happens in the green environment and once it is fully tested, we can switch the router so all incoming requests now go to Green instead of blue. Green is now live and Blue is idle. For more details, please refer pivotal resource link -  https://docs.pivotal.io/pivotalcf/2-5/devguide/deploy-apps/blue-green.html