Merge branch 'switch-methods-levels-k8s' into 'master'

Switch around Kubernetes Cluster Methods and Levels

See merge request gitlab-org/gitlab!69483

doc/user/project/clusters/index.md

@@ -54,21 +54,9 @@ Some GitLab features may support versions outside the range provided here.
 
 ## Add and remove clusters
 
-You can create new or add existing clusters to GitLab through different levels,
+You can create new or add existing clusters to GitLab through different [levels](#cluster-levels),
 using different methods.
 
-### Cluster levels
-
-You can connect clusters to GitLab in different levels, according to their purpose:
-
-- On the project level, to have a cluster dedicated to a project.
-- On the [group level](../../group/clusters/index.md), to use the same cluster across multiple projects within your group.
-- On the [instance level](../../instance/clusters/index.md), to use the same cluster across multiple groups and projects. **(FREE SELF)**
-
-### Methods to create new clusters
-
-To create new clusters, we **recommend** using [Infrastructure as Code](../../infrastructure/index.md).
-
 ### Methods to connect existing clusters
 
 To safely connect and configure an existing cluster on the **project level**, we
@@ -80,6 +68,18 @@ You can use [cluster certificates](add_existing_cluster.md) to connect
 clusters in all levels (projects, group, instance). However, for
 [security implications](#security-implications), this method is no longer recommended.
 
+### Methods to create new clusters
+
+To create new clusters, we **recommend** using [Infrastructure as Code](../../infrastructure/index.md).
+
+### Cluster levels
+
+You can connect clusters to GitLab in different levels, according to their purpose:
+
+- On the project level, to have a cluster dedicated to a project.
+- On the [group level](../../group/clusters/index.md), to use the same cluster across multiple projects within your group.
+- On the [instance level](../../instance/clusters/index.md), to use the same cluster across multiple groups and projects. **(FREE SELF)**
+
 ## Security implications
 
 WARNING: