[Explore] Audit all CRDs to ensure they record a useful status condition

[davewalter]

Background

We have (repeatedly) noted at our working group meetings (see here and here) that some of the CRDs are missing useful status information that would indicate whether a resource has been reconciled and, if so, what the current state of the resource is.

For this exploration, we want to answer the following questions for each CRD in Korifi:

• Does the status include an observed generation status?
• Would an observed generation status be useful for debugging?
• Does it have a high-level status condition such as Ready, Succeeded, or Valid?
• Does it "bubble up" the status of child resources (for example, Image -> BuildWorkload -> CFBuild -> CFApp)?

Acceptance Criteria

The outcome of this exploration should be a document containing the following information for each CRD defined in Korifi:

• the answers to the above questions
• a list of all the status conditions defined, including their possible values and whether a particular value is terminal or not

Timebox

No timebox

Dev Notes

• See the notes about status conditions in the Kubernetes API Conventions doc.

[gcapizzi]

@davewalter is this actually done, or do you plan to work on the document about status conditions? I moved this to Reviewer approved because of the merged PR, but I now see this might not be done.