Fix 404 in CRD generated documentation.

- Updated gen-crd-api-reference-docs
- Added our own config to point to the version of K8s we want.
- Manually updated the older CRD ref to point to 1.15, since it doesn't
get updated automatically.
- Added the ability to the htmltest config to disable external testing,
  for easier local dev testing.

Closes googleforgames#1617

build/build-image/Dockerfile

@@ -89,7 +89,7 @@ RUN curl -sL https://deb.nodesource.com/setup_12.x | bash - && \
 
 # install API reference docs generator
 RUN mkdir -p /go/src/github.com/ahmetb && \
-    cd /go/src/github.com/ahmetb && git clone -b v0.1.1 https://github.com/ahmetb/gen-crd-api-reference-docs && \
+    cd /go/src/github.com/ahmetb && git clone -b v0.2.0 https://github.com/ahmetb/gen-crd-api-reference-docs && \
     cd ./gen-crd-api-reference-docs && go build
 
 # html checker

site/assets/templates/pkg.tpl

@@ -5,29 +5,31 @@
 <ul>
     {{ range . }}
     <li>
-        <a href="#{{- packageDisplayName . -}}">{{ packageDisplayName . }}</a>
+        <a href="#{{- packageAnchorID . -}}">{{ packageDisplayName . }}</a>
     </li>
     {{ end }}
 </ul>
 {{ end}}
 
 {{ range .packages }}
-    <h2 id="{{- packageDisplayName . -}}">
+    <h2 id="{{- packageAnchorID . -}}">
         {{- packageDisplayName . -}}
     </h2>
 
-    {{ with .DocComments }}
-    <p>
-        {{ safe (renderComments .) }}
-    </p>
+    {{ with (index .GoPackages 0 )}}
+        {{ with .DocComments }}
+        <p>
+            {{ safe (renderComments .) }}
+        </p>
+        {{ end }}
     {{ end }}
 
     Resource Types:
     <ul>
     {{- range (visibleTypes (sortedTypes .Types)) -}}
         {{ if isExportedType . -}}
         <li>
-            <a href="#{{ typeIdentifier . }}">{{ typeIdentifier . }}</a>
+            <a href="{{ linkForType . }}">{{ typeDisplayName . }}</a>
         </li>
         {{- end }}
     {{- end -}}

site/content/en/docs/Advanced/limiting-resources.md

@@ -19,7 +19,7 @@ Kubernetes documentation for more details on "requests" and "limits" to both CPU
 
 ## GameServers
 
-Since the `GameServer` specification provides a full [`PodSpecTemplate`](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.10/#podtemplatespec-v1-core),
+Since the `GameServer` specification provides a full [`PodSpecTemplate`](https://v1-15.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#podtemplatespec-v1-core),
 we can take advantage of both resource limits and requests in our `GameServer` configurations. 
 
 For example, to set a CPU limit on our `GameServer` configuration of `250m/0.25` of a CPU,

site/content/en/docs/Guides/Client SDKs/_index.md

@@ -277,7 +277,7 @@ If `GameServer.Status.Players.IDs` is set manually through the Kubernetes API, u
 or SDK.WatchGameServer() instead to list the connected players.
 {{< /alert >}}
 
-[playerstatus]: {{< ref "/docs/Reference/agones_crd_api_reference.html#PlayerStatus" >}}
+[playerstatus]: {{< ref "/docs/Reference/agones_crd_api_reference.html#agones.dev/v1.PlayerStatus" >}}
 
 ## Writing your own SDK
 

site/content/en/docs/Guides/Client SDKs/rest.md

@@ -310,4 +310,4 @@ Response:
 {"list":["uzh7i","3zh7i"]}
 ```
 
-[playerstatus]: {{< ref "/docs/Reference/agones_crd_api_reference.html#PlayerStatus" >}}
+[playerstatus]: {{< ref "/docs/Reference/agones_crd_api_reference.html#agones.dev/v1.PlayerStatus" >}}