[v9] Split the Helm chart reference

docs/config.json

@@ -386,7 +386,17 @@
         },
         {
           "title": "Helm Chart Reference",
-          "slug": "/kubernetes-access/helm/reference/"
+          "slug": "/kubernetes-access/helm/reference/",
+          "entries": [
+            {
+              "title": "teleport-cluster",
+              "slug": "/kubernetes-access/helm/reference/teleport-cluster/"
+            },
+            {
+               "title": "teleport-kube-agent",
+               "slug": "/kubernetes-access/helm/reference/teleport-kube-agent/"
+            }
+          ]
         },
         {
           "title": "Access Controls",

docs/pages/kubernetes-access/getting-started/agent.mdx

@@ -162,4 +162,4 @@ $ kubectl get pods
 
 ## Next Steps
 
-- Take a look at a [kube-agent helm chart reference](../helm/reference.mdx#teleport-kube-agent) for a full list of parameters.
+- Take a look at a [kube-agent helm chart reference](../helm/reference/teleport-kube-agent.mdx) for a full list of parameters.

docs/pages/kubernetes-access/helm/guides/aws.mdx

@@ -525,9 +525,8 @@ $ helm --namespace cert-manager uninstall cert-manager
 
 ## Next steps
 
-You can follow our [Getting Started with Teleport guide](../../../setup/guides/docker.mdx#step-34-creating-a-teleport-user) to finish setting up your
+- You can follow our [Getting Started with Teleport guide](../../../setup/guides/docker.mdx#step-34-creating-a-teleport-user) to finish setting up your
 Teleport cluster.
+- See the [high availability section of our Helm chart reference](../reference/teleport-cluster.mdx#highavailability) for more details on high availability.
+- Read the [`cert-manager` documentation](https://cert-manager.io/docs/).
 
-See the [high availability section of our Helm chart reference](../reference.mdx#highavailability) for more details on high availability.
-
-Reference: [`cert-manager` docs](https://cert-manager.io/docs/).

docs/pages/kubernetes-access/helm/guides/gcp.mdx

@@ -409,7 +409,7 @@ To make changes to your Teleport cluster after deployment, you can use `helm upg
 Helm defaults to using the latest version of the chart available in the repo, which will also correspond to the latest
 version of Teleport. You can make sure that the repo is up to date by running `helm repo update`.
 
-If you want to use a different version of Teleport, set the [`teleportVersionOverride`](../reference.mdx#teleportversionoverride) value.
+If you want to use a different version of Teleport, set the [`teleportVersionOverride`](../reference/teleport-cluster.mdx#teleportversionoverride) value.
 
 Here's an example where we set the chart to use 3 replicas:
 
@@ -463,4 +463,4 @@ $ helm --namespace cert-manager uninstall cert-manager
 You can follow our [Getting Started with Teleport guide](../../../setup/guides/docker.mdx#step-34-creating-a-teleport-user) to finish setting up your
 Teleport cluster.
 
-See the [high availability section of our Helm chart reference](../reference.mdx#highavailability) for more details on high availability.
+See the [high availability section of our Helm chart reference](../reference/teleport-cluster.mdx#highavailability) for more details on high availability.

docs/pages/kubernetes-access/helm/includes/teleport-cluster-cloud-warning.mdx

@@ -6,5 +6,5 @@ Since the Auth and Proxy Services are fully managed in Teleport Cloud, you shoul
 
 You can use the `teleport-kube-agent` chart to enable the Application Service and Database Service in addition to the Kubernetes Service.
 
-For more information, see our [Helm chart reference](../reference.mdx#teleport-kube-agent).
+For more information, see our [Helm chart reference](../reference/teleport-kube-agent.mdx).
 </Details>