update aggregator to match latest kube

[deads2k]

This updates openshift to use the latest aggregation APIs.

@liggitt I didn't add comments in the existing groups, since we aren't going to have new versions in openshfit for a while.

[deads2k]

@jpeeler @sdodson @pmorie @derekwaynecarr @bparees @Kargakis

Be aware that the schema for APIService is being bumped to beta and being changed to match the (hopefully) final state in kube 1.7.

[bparees]

uh. so i need to go update all my cluster up stuff to use v1beta1 instead of v1alpha1?

[sdodson]

@ewolinetz fyi

[deads2k]

uh. so i need to go update all my cluster up stuff to use v1beta1 instead of v1alpha1?

And you need groupPriorityMinimum and versionPriority instead of priority.

[bparees]

@deads2k how soon can we get this in the queue? i can't put the cluster up PR in the merge queue until this goes in.

[liggitt]

@deads2k all the generated.pb.go changes with no accompanying descriptor changes are unexpected. what version of go did you run with? (and/or did you clean the built proto-generating tools after switching go versions) (gzip differences will output different gzipped manifests)

[liggitt]

just the question on the generated.pb.go changes, LGTM otherwise

[deads2k]

just the question on the generated.pb.go changes, LGTM otherwise

@liggitt grrrr. Probably 1.8. Just normal kube env.

[deads2k]

reran with 1.7, no changes.

[test]

[deads2k]

[merge]

[openshift-bot]

continuous-integration/openshift-jenkins/merge Waiting: You are in the build queue at position: 12

[openshift-bot]

Evaluated for origin merge up to c7463bc

[smarterclayton]

[test]

[openshift-bot]

Evaluated for origin test up to 3d93cfb

[openshift-bot]

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/2304/) (Base Commit: a68db68) (PR Branch Commit: 3d93cfb)

[deads2k]

@smarterclayton green if you're still manually tending