Update API reference to contain API group and versino info

The updated reference is generated using the kubernetes-sigs/reference-docs#172
change.

static/docs/reference/generated/kubernetes-api/v1.19/index.html

@@ -15,6 +15,9 @@
 <UL>
  <LI class="nav-level-1 strong-nav"><A href="#-strong-api-overview-strong-" class="nav-item"><STRONG>Overview</STRONG></A></LI>
 </UL>
+<UL>
+ <LI class="nav-level-1 strong-nav"><A href="#-strong-api-groups-strong-" class="nav-item"><STRONG>API Groups</STRONG></A></LI>
+</UL>
 <UL>
  <LI class="nav-level-1 strong-nav"><A href="#-strong-workloads-apis-strong-" class="nav-item"><STRONG>WORKLOADS APIS</STRONG></A></LI>
 </UL>
@@ -3486,7 +3489,7 @@
  <a href="https://github.com/kubernetes/kubernetes">Copyright 2016-2020 The Kubernetes Authors.</a>
   </DIV>
   <DIV class="col-md-6 text-right">
-    <DIV>Generated at: 2020-08-13 16:44:39 (EDT)</DIV>
+    <DIV>Generated at: 2020-10-19 15:00:27 (CST)</DIV>
     <DIV>API Version: <a href="https://github.com/kubernetes/kubernetes/blob/release-1.19/api/openapi-spec/swagger.json">v1.19.0</a></DIV>
   </DIV>
 </DIV><H1 id="-strong-api-overview-strong-"><STRONG>API OVERVIEW</STRONG></H1>
@@ -3577,6 +3580,34 @@ <H4 id="resource-operations-additional">Additional Operations</H4>
 	<LI><B>Read / Write Status</B>: Read or Update the Status for a resource object.  The Status can only changed through these update operations.</LI>
 </UL>
 <HR />
+<H1 id="-strong-api-groups-strong-"><STRONG>API Groups</STRONG></H1>
+<P>The API Groups and their versions are summarized in the following table.</P><TABLE class="col-md-8">
+<THEAD><TR><TH>Group</TH><TH>Version</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>authentication.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v1, v2beta2, v2beta1</CODE></TD></TR>
+<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1, v1beta1, v2alpha1</CODE></TD></TR>
+<TR><TD><CODE>certificates.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>coordination.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD></TR>
+<TR><TD><CODE>events.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD></TR>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD></TR>
+<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1beta1, v1alpha1</CODE></TD></TR>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD></TR>
+<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1, v1beta1, v1alpha1</CODE></TD></TR>
+<TR><TD><CODE>scheduling.k8s.io</CODE></TD><TD><CODE>v1, v1beta1, v1alpha1</CODE></TD></TR>
+<TR><TD><CODE>settings.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD></TR>
+<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1, v1beta1, v1alpha1</CODE></TD></TR>
+</TBODY>
+</TABLE>
 <H1 id="-strong-workloads-apis-strong-"><STRONG>WORKLOADS</STRONG></H1>
 
 <P>Workloads resources are responsible for managing and running your containers on the cluster. <A href="#container-v1-core">Containers</A> are created