Fix "kubectl explain" output for Agones CRDs

[jiwonaid]

What type of PR is this?

Uncomment only one /kind <> line, press enter to put that in a new line, and remove leading whitespace from that line:

/kind breaking
/kind bug
/kind cleanup
/kind documentation

/kind feature

/kind hotfix

What this PR does / Why we need it:

To support "kubectl explain" command for Agones CRDs, some yaml values are added.

(kubernetes-admin-dev@dev) ☁  ~  kubectl explain pod
KIND:     Pod
VERSION:  v1

DESCRIPTION:
     Pod is a collection of containers that can run on a host. This resource is
     created by clients and scheduled onto hosts.

This is the result for the Fleet after applying this PR.

(kubernetes-admin-dev@dev) ☁  ~  kubectl version --short
Client Version: v1.22.3
Server Version: v1.19.6

(kubernetes-admin-dev@dev) ☁  ~  kubectl explain fleet
KIND:     Fleet
VERSION:  agones.dev/v1

DESCRIPTION:
     Fleet is the data structure for a Fleet resource

FIELDS:
   apiVersion	<string>
     APIVersion defines the versioned schema of this representation of an
     object. Servers should convert recognized schemas to the latest internal
     value, and may reject unrecognized values. More info:
     https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources

   kind	<string>
     Kind is a string value representing the REST resource this object
     represents. Servers may infer this from the endpoint the client submits
     requests to. Cannot be updated. In CamelCase. More info:
     https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds

   metadata	<Object>
     Standard object's metadata. More info:
     https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

   spec	<Object>
     FleetSpec is the spec for a Fleet. More info:
     https://agones.dev/site/docs/reference/agones_crd_api_reference/#agones.dev/v1.Fleet

   status	<Object>
     FleetStatus is the status of a Fleet. More info:
     https://agones.dev/site/docs/reference/agones_crd_api_reference/#agones.dev/v1.Fleet

Which issue(s) this PR fixes:

Closes #1194

Special notes for your reviewer:

Hello.
For your information, I turned off my editor's auto-formatting features for the 'install/yaml/install.yaml', because I was not sure about that.

[agones-bot]

Build Failed 😱

Build Id: da0433da-bad7-4107-aff1-d0bd201d079b

• Cloud Build view
• Cloud Build log download

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

[roberthbailey]

Thanks for your contribution!

The automated tests failed because install.yaml is a generated file and sometimes when you try to hand-edit it you don't exactly match what gets generated (in your case it looks like whitespace differences):

diff /tmp/agones-install/install.yaml.sorted /tmp/agones-install/install.current.yaml.sorted
11751c11751
<                               type: string 
---
>                               type: string
11981c11981
<                              type: string 
---
>                              type: string
12452a12453
>                         https://agones.dev/site/docs/reference/agones_crd_api_reference/#agones.dev/v1.GameServer'
12520a12522
>                        https://agones.dev/site/docs/reference/agones_crd_api_reference/#agones.dev/v1.GameServer'
12586a12589
>                       description: 'GameServerSpec is the spec for a GameServer resource. More info:
12634a12638
>                      description: 'GameServerSpec is the spec for a GameServer resource. More info:
12688c12692
<                      type: string 
---
>                      type: string
12744a12749
>                   description: 'GameServer is the data structure for a GameServer resource.'
12810a12816
>                  description: 'GameServer is the data structure for a GameServer resource.'

Rather than editing it by hand, if you edit the helm files and then run make gen-install that should clear up the test failures.

[agones-bot]

Build Succeeded 👏

Build Id: 46381256-5c11-4d76-8d3b-3ffe8aac7c0f

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

• image: gcr.io/agones-images/agones-controller:1.20.0-0dbaa06
• image: gcr.io/agones-images/agones-ping:1.20.0-0dbaa06
• Linux C++ SDK (build): agonessdk-1.20.0-0dbaa06-linux-arch_64.tar.gz
• SDK Server: agonessdk-server-1.20.0-0dbaa06.zip

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

• https://0dbaa06-dot-preview-dot-agones-images.appspot.com/

To install this version:

• git fetch https://github.com/googleforgames/agones.git pull/2423/head:pr_2423 && git checkout pr_2423
• helm install ./install/helm/agones --namespace agones-system --name agones --set agones.image.tag=1.20.0-0dbaa06

[jiwonaid]

Thanks for your code review! @roberthbailey

The generated install.yaml file was pushed and the build is just succeeded.

Thank you.

[markmandel]

Oh that's neat!

[markmandel]

Just took this for a spin - looks good to me!

[agones-bot]

Build Succeeded 👏

Build Id: 548a7678-699e-478a-ac6c-d360b23f2783

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

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

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

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

To install this version:

• git fetch https://github.com/googleforgames/agones.git pull/2423/head:pr_2423 && git checkout pr_2423
• helm install ./install/helm/agones --namespace agones-system --name agones --set agones.image.tag=1.21.0-f96a6e9

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jiwonaid, markmandel, roberthbailey

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [markmandel,roberthbailey]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment