Spec is nice, but status is twice as nice

[n3wscott]

In kube-native resource definitions, we see a lot of implementations that neglect to define the expected shape of the status, but it is vital as the specification to define the minimum shape expected for a status of an observed resource.spec. Without this, observers of the resource will be unable to reconcile their state with the resource.

I recommend adding metadata.generation, this is the mutation count for .spec changes.

Then the minimum .status shape should be:

status:
  observedGeneration: <int> # generation of observed spec of resource.
  conditions:                            # array of conditions
    - lastTransitionTime: <datetime> # in kube api datetime of last meaningful transition of status.
      status: <triloolean> # "True", "False", "Unknown"
      type: Ready # the string "Ready"