Condition
Conditions show the status of reconciliation progress on a given resource.
Most resource use a top-level condition type "Ready" or "Completed" to show overall status with other conditions to checkpoint each stage of reconciliation. Note that if metadata.Generation does not equal status.ObservedGeneration, the conditions shown may not be relevant for the current spec.
| JSON representation |
|---|
{ "type": string, "status": string, "reason": string, "message": string, "lastTransitionTime": string, "severity": string } |
| Fields | |
|---|---|
type |
type is used to communicate the status of the reconciliation process. Types common to all resources include: * "Ready" or "Completed": True when the Resource is ready. |
status |
Status of the condition, one of True, False, Unknown. |
reason |
Optional. One-word CamelCase reason for the condition's last transition. These are intended to be stable, unique values which the client may use to trigger error handling logic, whereas messages which may be changed later by the server. |
message |
Optional. Human readable message indicating details about the current status. |
lastTransitionTime |
Optional. Last time the condition transitioned from one status to another. Uses RFC 3339, where generated output will always be Z-normalized and use 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: |
severity |
Optional. How to interpret this condition. One of Error, Warning, or Info. Conditions of severity Info do not contribute to resource readiness. |