Joel Baxter

Generally speaking I think we need to add this logic to the flow: First of all, there's the spot where we completely avoid all of the setup logic in handleCreatingMembers...

Related to issue #229. The consensus at the moment seems to be that: * The distroID property is used to identify app CRs that are "for the same app" even...

Developing this as part of our live app upgrade work, so it is also reasonable to expect this for the 1.0 release.

A kdapp resource has a distro ID and a version. When it is deployed into K8s it also gains a name and a namespace. If multiple kdapp resources (with different...

Other considerations: * Should we allow the kdcluster to be initially created in a paused state? What about if it is in the middle of some other reconfiguration? It would...

I think we can actually lift a lot of the ideas/decisions from the live-upgrade feature to answer those questions. I.e., only allow pause for a stable configured kdcluster and don't...

Going to see if I can look at this for a near-term release like 0.11.0.

I'm going to take this off of the 0.3 milestone unless some additional motivation for the change pops up.

If we're gonna do this, need to do it. Assigning to 0.7.0 for now.

Rather than parallelize syncMembers yet, we could instead move to using fire-and-forget startscripts. Start them running nohup'ed inside the container, then just come back around to check on their results...