Deployment Configuration for auto-Evoke configure of Conjur Master in OpenShift

deploymentConfig.yml

apiVersion: v1
kind: DeploymentConfig
metadata:
  annotations:
    openshift.io/generated-by: OpenShiftWebConsole
  creationTimestamp: '2018-02-14T01:32:41Z'
  generation: 5
  labels:
    app: conjur-master
  name: conjur-master
  namespace: conjurdemo
  resourceVersion: '32978'
  selfLink: /oapi/v1/namespaces/conjurdemo/deploymentconfigs/conjur-master
  uid: f2f20b0d-1126-11e8-9b4e-962ce123f21b
spec:
  replicas: 1
  selector:
    app: conjur-master
    deploymentconfig: conjur-master
  strategy:
    activeDeadlineSeconds: 21600
    resources: {}
    rollingParams:
      intervalSeconds: 1
      maxSurge: 25%
      maxUnavailable: 25%
      timeoutSeconds: 600
      updatePeriodSeconds: 1
    type: Rolling
  template:
    metadata:
      annotations:
        openshift.io/generated-by: OpenShiftWebConsole
      creationTimestamp: null
      labels:
        app: conjur-master
        deploymentconfig: conjur-master
    spec:
      containers:
        - image: >-
            172.30.1.1:5000/conjurdemo/conjur-appliance@sha256:d382dd97b974247b5132ae31e45e2c9b4f6963920468729102e6d9ab4dfc37d2
          imagePullPolicy: Always
          name: conjur-master
          ports:
            - containerPort: 22
              protocol: TCP
            - containerPort: 443
              protocol: TCP
            - containerPort: 636
              protocol: TCP
            - containerPort: 5432
              protocol: TCP
            - containerPort: 5433
              protocol: TCP
            - containerPort: 38053
              protocol: TCP
###### CHANGES BEGIN HERE
###### ADDING READINESS PROBE
          readinessProbe:
            exec:
              command:
                - evoke
                - configure
                - master
                - '-h'
                - conjur-master
                - '-p'
                - Cyberark1
                - minishift-demo
            failureThreshold: 3
            periodSeconds: 300
            successThreshold: 1
            timeoutSeconds: 900
###### END CHANGES
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30
  test: false
  triggers:
    - type: ConfigChange
    - imageChangeParams:
        automatic: true
        containerNames:
          - conjur-master
        from:
          kind: ImageStreamTag
          name: 'conjur-appliance:latest'
          namespace: conjurdemo
        lastTriggeredImage: >-
          172.30.1.1:5000/conjurdemo/conjur-appliance@sha256:d382dd97b974247b5132ae31e45e2c9b4f6963920468729102e6d9ab4dfc37d2
      type: ImageChange
status:
  availableReplicas: 1
  conditions:
    - lastTransitionTime: '2018-02-14T01:36:08Z'
      lastUpdateTime: '2018-02-14T01:36:08Z'
      message: Deployment config does not have minimum availability.
      status: 'False'
      type: Available
    - lastTransitionTime: '2018-02-14T01:36:08Z'
      lastUpdateTime: '2018-02-14T01:36:08Z'
      message: replication controller "conjur-master-2" is progressing
      reason: ReplicationControllerUpdated
      status: 'True'
      type: Progressing
  details:
    causes:
      - type: ConfigChange
    message: config change
  latestVersion: 2
  observedGeneration: 5
  readyReplicas: 1
  replicas: 1
  unavailableReplicas: 1
  updatedReplicas: 1