Promote autoscaling to v1

[roberthbailey]

This is part of #703.

I didn't update agones_crd_api_reference.html because I was hoping that there is an automated way to do it that I haven't yet found (although the presence of {{% feature expiryVersion="0.10.0" %}} at the top of the file makes me think I may have unfounded hope...).

I also fixed some import naming as suggested by @pooneh-m in #829 to try and clean up some tech debt while I was at it.

/assign @markmandel

/label kind/breaking

[agones-bot]

Build Failed 😱

Build Id: ea9de890-036f-4a9c-9a96-6e4dbb54c808

• Cloud Build view
• Cloud Build log download

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

[aLekSer]

Hello @roberthbailey let me check what have happened with agones_crd_api_reference.html.

[aLekSer]

Verified on your branch - all is fine with make gen-api-docs. However I think we could remove outdated versions with expiryVersion < current version - 1 minor version.
Produced a fix for generation process, removed annoying old versions:
#877

[roberthbailey]

Thanks @aLekSer! Once #877 goes in I will re-generate API docs. In the mean time I'll try to get all of the presubmit tests passing.

[agones-bot]

Build Failed 😱

Build Id: fb5449bf-6c86-4a5c-992a-c2c1107ef445

• Cloud Build view
• Cloud Build log download

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

[agones-bot]

Build Failed 😱

Build Id: 78c5af59-5c35-4ca7-b756-fd0421f74190

• Cloud Build view
• Cloud Build log download

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

[roberthbailey]

@markmandel - it looks like the e2e test uses helm upgrade which as expected fails since I've changed api groups. Doing a fresh helm install with

helm install --name autoscaling-v1 --namespace agones-system agones --set agones.image.tag=0.12.0-097a5ea,agones.image.registry=gcr.io/agones-images

on a new cluster worked for me, so I'm guessing that someone with admin access to the agones-images will need to modify the cluster used by cloud build for e2e testing to delete the existing helm install so a fresh one will succeed.

It looks like in #829 you did a helm delete agones -purge at one point, but it isn't clear if that was necessary for tests to pass or not.

[agones-bot]

Build Failed 😱

Build Id: 2d8268a6-6210-4ca4-94ce-3b143f4016e8

• Cloud Build view
• Cloud Build log download

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

[agones-bot]

Build Failed 😱

Build Id: c2232a41-2fd4-4103-80bf-493ad89e1670

• Cloud Build view
• Cloud Build log download

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

[markmandel]

This looks good to me - happy to approve it 👍

[agones-bot]

Build Succeeded 👏

Build Id: adeec71a-b0e3-4007-aa00-8624bfadf973

The following development artifacts have been built, and will exist for the next 30 days:

• image: gcr.io/agones-images/agones-controller:0.12.0-61ac72d
• image: gcr.io/agones-images/agones-sdk:0.12.0-61ac72d
• image: gcr.io/agones-images/agones-ping:0.12.0-61ac72d
• Linux C++ SDK (build): agonessdk-0.12.0-61ac72d-linux-arch_64.tar.gz
• SDK Server: agonessdk-server-0.12.0-61ac72d.zip

A preview of the website (the last 30 builds are retained):

• https://61ac72d-dot-preview-dot-agones-images.appspot.com/

To install this version:

• git fetch https://github.com/GoogleCloudPlatform/agones.git pull/874/head:pr_874 && git checkout pr_874
• helm install install/helm/agones --namespace agones-system --name agones --set agones.image.tag=0.12.0-61ac72d