`sc install` on GKE 1.11.2-gke.18 fails with unknown field "priority"

[fruwe]

It seems, that sc install fails on a new cluster.

I created a new cluster like this:

    gcloud beta container clusters create "my_cluster_name" \
      --addons HorizontalPodAutoscaling,HttpLoadBalancing \
      --cluster-version "1.11.2-gke.18" \
      --disk-size "100" \
      --disk-type "pd-standard" \
      --enable-autorepair \
      --enable-autoscaling --min-nodes "3" --max-nodes "20" \
      --enable-autoupgrade \
      --enable-ip-alias \
      --enable-stackdriver-kubernetes \
      --image-type "COS" \
      --machine-type "custom-1-6656" \
      --network "default" \
      --no-enable-basic-auth \
      --num-nodes "3" \
      --scopes "https://www.googleapis.com/auth/cloud-platform" \
      --subnetwork "default"

After that, I expected to sc install to install the service catalog, but it fails with the following message:

[15:09:10] blackfalcon:~/go/src/github.com/GoogleCloudPlatform/k8s-service-catalog/installer :chris $ output/bin/sc install
account: xx@yy.com
project: zzz-project
zone: asia-northeast1-a
generated service catalog deployment config in dir: /tmp/service-catalog379525118
Service Catalog could not be installed.
Error: error deploying YAML files: deploy failed with output: exit status 1 :error: error validating "/tmp/service-catalog379525118/api-registration.yaml": error validating data: ValidationError(APIService.spec): unknown field "priority" in io.k8s.kube-aggregator.pkg.apis.apiregistration.v1beta1.APIServiceSpec; if you choose to ignore these errors, turn validation off with --validate=false

It seems, that the priority field is no longer supported (or was never in the first place)

[khipkin]

Looks like this was fixed by #217