oc cluster up: use registry and router deployment commands from the image being deployed

[csrwng]

Recent changes to the router deployment config make the released oc binary (v3.6.0-alpha.2) incompatible with the latest router image. The deployment config used by the older oc binary for the router causes the router to fail health checks and eventually die. Going forward we can prevent this by invoking the oc adm router and oc adm registry commands on the origin container itself instead of using the in-process command from the oc client running cluster up.

[csrwng]

/cc @bparees @smarterclayton @cfchase

[jwmatthews]

@csrwng thank you for the help in debugging this

[smarterclayton]

This is correct. We should probably also use the templates vendored in the image as well. On Jul 6, 2017, at 10:18 PM, OpenShift Bot <notifications@github.com> wrote: Closed #14913 <#14913> via #15087 <#15087>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14913 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABG_p7_66Nq1QSgn2rNQhJd6e-P860MKks5sLZVmgaJpZM4OGs9R> .