...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
status:
conditions:
- lastProbeTime: null
lastTransitionTime: "2019-07-19T21:47:51Z"
status: "True"
type: Initialized
- lastProbeTime: null
lastTransitionTime: "2019-07-19T21:48:55Z"
status: "True"
type: Ready
- lastProbeTime: null
lastTransitionTime: "2019-07-19T21:48:55Z"
status: "True"
type: ContainersReady
- lastProbeTime: null
lastTransitionTime: "2019-07-19T21:47:50Z"
status: "True"
type: PodScheduled
containerStatuses:
- containerID: docker://eb3f5ae847a5a3aa38c95cba3aea0bf6a15fce12bcd220206de8b513c481154f
image: edgexfoundry/docker-edgex-mongo:0.8.0
imageID: docker-pullable://edgexfoundry/docker-edgex-mongo@sha256:e2cf9380555867ed747be392284117be3b50cfdff04e13e6f57cb51d86f331b3
lastState: {}
name: edgex-mongo
ready: true
restartCount: 0
state:
running:
startedAt: "2019-07-19T21:48:27Z"
hostIP: 172.25.55.139
phase: Running
podIP: 10.42.0.13
qosClass: BestEffort
startTime: "2019-07-19T21:47:51Z" |
Given this disparate nature of Status' we need to filter the list of resources we update status for and figure out a way to summarize this status to a simple Ready|Pending|Failed status.
Eg:
- A deployment status would be READY if replicas == readyReplicas
- A POD status would be READY if all its containerStatuses have ready:True