Do we need both ContainerHealthy / ResourcesAvailable conditions?

[mattmoor]

Going through #1118 I found that there is really a single point at which we determine ContainerHealthy and ResourcesAvailable, so I'm wondering whether these should be coalesced into a single condition, or whether we should continue to have distinct conditions for them.

This feels related to the ongoing discussion around conditions. cc @cooperneil @sixolet @evankanderson @tcnghia

[mattmoor]

/assign @jonjohnsonjr

Can you do some research on the existing Kubernetes wisdom here, and come up with a proposal we can implement post-0.1?

@smarterclayton linked some materials in the WG notes from when we discussed this about a month ago (around the time this was opened).

[jonjohnsonjr]

For my own future reference, WG notes here.

[mattmoor]

Moving this into v1 where we should spend some time reconsidering some of our condition types.

[mattmoor]

... as part of the "Serving API v1" track.