Integration: There should be an easy way check the process state

[kubernetes-retired]

Integration: There should be an easy way check the process state

[munnerz]

In the Etcd case, it'd be great to also get access to the URL that has been selected.

Currently, there's no way to take advantage of the auto generated client URL without using the ControlPlane structure, as processState is not exported and is what contains the URL (the field is not copied back to the Etcd struct after generation right now).

[totherme]

I've begun a little exploration of what this might look like here. Comments very welcome!

[hoegaarden]

@munnerz I did the same exploration as @totherme but with a bit of a different approach. I took your words literally and, after defaulting, copy certain interesting things back from the ProcessState to the actual struct (APIServer & Etcd)

Comparing this implementation with @totherme's I see the following pros and cons:

• Pro: not changing the public interface too much (only adding the optional io.Writers for Std{Out,Err}
• Con: Having somewhat strange "pointer magick" for the copy-back of interesting things

@munnerz which one do you prefer?

To compare the two approaches, here are the diffs for both:

• @hoegaarden: master...hoegaarden:expose_IO_and_URL
• @totherme: master...totherme:process-state