Change some links to new api reference

content/en/docs/concepts/architecture/nodes.md

@@ -242,7 +242,7 @@ checks the state of each node every `--node-monitor-period` seconds.
 Heartbeats, sent by Kubernetes nodes, help determine the availability of a node.
 
 There are two forms of heartbeats: updates of `NodeStatus` and the
-[Lease object](/docs/reference/generated/kubernetes-api/{{< latest-version >}}/#lease-v1-coordination-k8s-io).
+{{< api-reference page="cluster-resources/lease-v1" >}} object.
 Each Node has an associated Lease object in the `kube-node-lease`
 {{< glossary_tooltip term_id="namespace" text="namespace">}}.
 Lease is a lightweight resource, which improves the performance

content/en/docs/concepts/cluster-administration/flow-control.md

@@ -194,10 +194,10 @@ that originate from outside your cluster.
 
 ## Resources
 The flow control API involves two kinds of resources.
-[PriorityLevelConfigurations](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#prioritylevelconfiguration-v1beta1-flowcontrol-apiserver-k8s-io)
+{{< api-reference page="cluster-resources/priority-level-configuration-v1beta1" >}}
 define the available isolation classes, the share of the available concurrency
 budget that each can handle, and allow for fine-tuning queuing behavior.
-[FlowSchemas](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#flowschema-v1beta1-flowcontrol-apiserver-k8s-io)
+{{< api-reference page="cluster-resources/flow-schema-v1beta1" >}}
 are used to classify individual inbound requests, matching each to a
 single PriorityLevelConfiguration.  There is also a `v1alpha1` version
 of the same API group, and it has the same Kinds with the same syntax and

content/en/docs/concepts/configuration/manage-resources-containers.md

@@ -673,7 +673,7 @@ the node.
 
 The amount of resources available to Pods is less than the node capacity, because
 system daemons use a portion of the available resources. The `allocatable` field
-[NodeStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#nodestatus-v1-core)
+{{< api-reference page="cluster-resources/node-v1" anchor="NodeStatus" >}}
 gives the amount of resources that are available to Pods. For more information, see
 [Node Allocatable Resources](https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md).
 
@@ -758,8 +758,8 @@ You can see that the Container was terminated because of `reason:OOM Killed`, wh
 * For more details about the difference between requests and limits, see
   [Resource QoS](https://git.k8s.io/community/contributors/design-proposals/node/resource-qos.md).
 
-* Read the [Container](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#container-v1-core) API reference
+* Read the {{< api-reference page="workloads-resources/container" >}} API reference
 
-* Read the [ResourceRequirements](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#resourcerequirements-v1-core) API reference
+* Read the {{< api-reference page="workloads-resources/container" anchor="ResourceRequirements" >}} API reference
 
 * Read about [project quotas](https://xfs.org/docs/xfsdocs-xml-dev/XFS_User_Guide/tmp/en-US/html/xfs-quotas.html) in XFS

content/en/docs/concepts/configuration/secret.md

@@ -54,7 +54,7 @@ precedence.
 ## Types of Secret {#secret-types}
 
 When creating a Secret, you can specify its type using the `type` field of
-the [`Secret`](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#secret-v1-core)
+the {{< api-reference page="config-and-storage-resources/secret-v1" >}}
 resource, or certain equivalent `kubectl` command line flags (if available).
 The Secret type is used to facilitate programmatic handling of the Secret data.
 
@@ -137,7 +137,7 @@ See the [ServiceAccount](/docs/tasks/configure-pod-container/configure-service-a
 documentation for more information on how service accounts work.
 You can also check the `automountServiceAccountToken` field and the
 `serviceAccountName` field of the
-[`Pod`](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core)
+{{< api-reference page="workloads-resources/pod-v1" >}}
 for information on referencing service account from Pods.
 
 ### Docker config Secrets
@@ -769,7 +769,7 @@ these pods.
 The `imagePullSecrets` field is a list of references to secrets in the same namespace.
 You can use an `imagePullSecrets` to pass a secret that contains a Docker (or other) image registry
 password to the kubelet. The kubelet uses this information to pull a private image on behalf of your Pod.
-See the [PodSpec API](/docs/reference/generated/kubernetes-api/{{< latest-version >}}/#podspec-v1-core) for more information about the `imagePullSecrets` field.
+See the {{< api-reference page="workloads-resources/pod-v1" anchor="PodSpec" >}} API for more information about the `imagePullSecrets` field.
 
 #### Manually specifying an imagePullSecret
 

content/en/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation.md

@@ -37,6 +37,6 @@ to disable the timeout restriction. This deprecated feature gate will be removed
 * To get the aggregator working in your environment, [configure the aggregation layer](/docs/tasks/extend-kubernetes/configure-aggregation-layer/).
 * Then, [setup an extension api-server](/docs/tasks/extend-kubernetes/setup-extension-api-server/) to work with the aggregation layer.
 * Also, learn how to [extend the Kubernetes API using Custom Resource Definitions](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/).
-* Read the specification for [APIService](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#apiservice-v1-apiregistration-k8s-io)
+* Read the specification for {{< api-reference page="cluster-resources/api-service-v1" >}}
 
 

layouts/shortcodes/api-reference.html

@@ -1,5 +1,6 @@
 {{ $base := "docs/reference/kubernetes-api" }}
 {{ $pageArg := .Get "page" }}
+{{ $anchorArg := .Get "anchor" }}
 {{ $page := site.GetPage "page" (printf "%s/%s" $base $pageArg) }}
 {{ $metadata := $page.Params.api_metadata }}
-<a href="{{ $page.URL }}">{{ $metadata.kind}}</a>
+<a href="{{ $page.URL }}{{if $anchorArg}}#{{ $anchorArg }}{{end}}">{{if $anchorArg}}{{ $anchorArg }}{{else}}{{ $metadata.kind }}{{end}}</a>