GKE scopes in installation and testing are overkill

[markmandel]

GKE scopes could be dropped to the new(?) gke-default scope, which is far less than what we have in either the documentation, our e2e cluster or development test clusters.

Likely only needs someone to test creating a cluster with the default scope, and making the changes in those three places.

[aLekSer]

Started working on that issue

[aLekSer]

Currently if omitting the oauthScopes in development test clusters. An error occurs Cannot pull image agones-controller from the registry.
And unauthorized error if executing docker run on one of cluster nodes.
Will check other places where we could use gke-default scope.

[markmandel]

@aLekSer does this mean the alias's don't work via the deployment manager, just through gcloud?

[aLekSer]

@markmandel I was not able to find out this yesterday. Will let you know. In Jinja template it seems that only https://www.googleapis.com/auth/compute style oauthScopes are accepted. If I pass gke-defaults.
Tested that I could pass it this way:

gcloud container clusters create [CLUSTER_NAME] --cluster-version=1.11 \
  --no-enable-legacy-authorization \
  --tags=game-server \
  --enable-basic-auth \
  --password=supersecretpassword \
  --scopes=gke-default \
  --num-nodes=3 \
  --machine-type=n1-standard-1

And after use install.yaml, cluster is working fine.
Please refer to NodeConfig. There is no option to add some keyword like gke-default in jinja config, but we can remove logging.write and monitoring ones.