O p enShift Container Platform 4.5 Applications In the above example, the  organization/strategy  container image provides the deployment behavior. The optional  command  array overrides any  CMD  directive specified in the image’s  Dockerfile . The optional environment variables provided are added to the execution environment of the strategy process. Additionally, OpenShift Container Platform provides the following environment variables to the deployment process: The replica count of the new deployment will initially be zero. The responsibility of the strategy is to make the new deployment active using the logic that best serves the needs of the user. Alternatively, use the  customParams  object to inject the custom deployment logic into the existing deployment strategies. Provide a custom shell script logic and call the  openshift-deploy  binary. Users do not have to supply their custom deployer container image; in this case, the default OpenShift Container Platform deployer image is used instead: This results in following deployment: Started deployment #2 --> Scaling up custom-deployment-2 from 0 to 2, scaling down custom-deployment-1 from 2 to 0  (keep 2 pods available, don't exceed 3 pods) Scaling custom-deployment-2 up to 1 --> Reached 50% (currently 50%) Halfway there --> Scaling up custom-deployment-2 from 1 to 2, scaling down custom-deployment-1 from 2 to 0  (keep 2 pods available, don't exceed 3 pods) Scaling custom-deployment-1 down to 1 Scaling custom-deployment-2 up to 2 strategy: type: Rolling customParams: command: - /bin/sh - -c -  | set -e openshift-deploy --until=50% echo Halfway there openshift-deploy echo Complete environment: - name: ENV_1 value: VALUE_1 Environment variable Description OPENSHIFT_DEPLOYMENT_ NAME The name of the new deployment, a replication controller. OPENSHIFT_DEPLOYMENT_ NAMESPACE The name space of the new deployment. 6 4