deploy: cleanup dc controller

[0xmichalis]

Since upstream are going to support up to two old releases, there is no
reason for us to continue supporting pre 1.1 clients. This commit makes
the deployment config controller a maintainable piece of code again after
a long time:)

@mfojtik @smarterclayton

[0xmichalis]

[test]

[smarterclayton]

Add a release note and @brenton that 3.1 -> 3.4 upgrade will not be allowed
directly.

On Oct 18, 2016, at 5:58 PM, Michail Kargakis notifications@github.com
wrote:

[test]

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#11426 (comment),
or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABG_p3RXk5CQ2Zdb0x4VrYX-uRtgAXdRks5q1UEggaJpZM4KaVn1
.

[brenton]

@smarterclayton, The upgrade playbooks today require that customers upgrade sequentially without skipping any steps.

[0xmichalis]

Release note added: openshift/openshift-docs#2933 (comment)

[0xmichalis]

#11240 [test]

[openshift-bot]

Evaluated for origin test up to 066150d

[openshift-bot]

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10448/) (Base Commit: 2016d68)

[mfojtik]

LGTM

[0xmichalis]

[merge]

[mfojtik]

approved for 3.4

[merge]

[openshift-bot]

Evaluated for origin merge up to 066150d

[openshift-bot]

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10448/) (Base Commit: 50efe7d) (Image: devenv-rhel7_5239)