Remove reference to archived repo

versioned_docs/version-2.0-2.4/how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-rke1-templates/infrastructure.md

@@ -50,11 +50,7 @@ When you need to make changes to your infrastructure, instead of manually updati
 
 - You can also modify auth in the Terraform provider.
 
-- You can reverse engineer how to do define a setting in Terraform by changing the setting in Rancher, then going back and checking your Terraform state file to see how it maps to the current state of your infrastructure.
-
-- If you want to manage Kubernetes cluster settings, Rancher settings, and hardware settings all in one place, use [Terraform modules](https://github.com/rancher/terraform-modules). You can pass a cluster configuration YAML file or an RKE template configuration file to a Terraform module so that the Terraform module will create it. In that case, you could use your infrastructure-as-code to manage the version control and revision history of both your Kubernetes cluster and its underlying hardware.
-
-## Tip for Creating CIS Benchmark Compliant Clusters
+- You can reverse engineer how to do define a setting in Terraform by changing the setting in Rancher, then going back and checking your Terraform state file to see how it maps to the current state of your infrastructure.## Tip for Creating CIS Benchmark Compliant Clusters
 
 This section describes one way that you can make security and compliance-related config files standard in your clusters.
 

versioned_docs/version-2.5/how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-rke1-templates/infrastructure.md

@@ -50,11 +50,7 @@ When you need to make changes to your infrastructure, instead of manually updati
 
 - You can also modify auth in the Terraform provider.
 
-- You can reverse engineer how to do define a setting in Terraform by changing the setting in Rancher, then going back and checking your Terraform state file to see how it maps to the current state of your infrastructure.
-
-- If you want to manage Kubernetes cluster settings, Rancher settings, and hardware settings all in one place, use [Terraform modules](https://github.com/rancher/terraform-modules). You can pass a cluster configuration YAML file or an RKE template configuration file to a Terraform module so that the Terraform module will create it. In that case, you could use your infrastructure-as-code to manage the version control and revision history of both your Kubernetes cluster and its underlying hardware.
-
-## Tip for Creating CIS Benchmark Compliant Clusters
+- You can reverse engineer how to do define a setting in Terraform by changing the setting in Rancher, then going back and checking your Terraform state file to see how it maps to the current state of your infrastructure.## Tip for Creating CIS Benchmark Compliant Clusters
 
 This section describes one way that you can make security and compliance-related config files standard in your clusters.
 

versioned_docs/version-2.6/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-rke1-templates/infrastructure.md

@@ -50,11 +50,7 @@ When you need to make changes to your infrastructure, instead of manually updati
 
 - You can also modify auth in the Terraform provider.
 
-- You can reverse engineer how to do define a setting in Terraform by changing the setting in Rancher, then going back and checking your Terraform state file to see how it maps to the current state of your infrastructure.
-
-- If you want to manage Kubernetes cluster settings, Rancher settings, and hardware settings all in one place, use [Terraform modules](https://github.com/rancher/terraform-modules). You can pass a cluster configuration YAML file or an RKE template configuration file to a Terraform module so that the Terraform module will create it. In that case, you could use your infrastructure-as-code to manage the version control and revision history of both your Kubernetes cluster and its underlying hardware.
-
-## Tip for Creating CIS Benchmark Compliant Clusters
+- You can reverse engineer how to do define a setting in Terraform by changing the setting in Rancher, then going back and checking your Terraform state file to see how it maps to the current state of your infrastructure.## Tip for Creating CIS Benchmark Compliant Clusters
 
 This section describes one way that you can make security and compliance-related config files standard in your clusters.
 

versioned_docs/version-2.7/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-rke1-templates/infrastructure.md

@@ -50,11 +50,7 @@ When you need to make changes to your infrastructure, instead of manually updati
 
 - You can also modify auth in the Terraform provider.
 
-- You can reverse engineer how to do define a setting in Terraform by changing the setting in Rancher, then going back and checking your Terraform state file to see how it maps to the current state of your infrastructure.
-
-- If you want to manage Kubernetes cluster settings, Rancher settings, and hardware settings all in one place, use [Terraform modules](https://github.com/rancher/terraform-modules). You can pass a cluster configuration YAML file or an RKE template configuration file to a Terraform module so that the Terraform module will create it. In that case, you could use your infrastructure-as-code to manage the version control and revision history of both your Kubernetes cluster and its underlying hardware.
-
-## Tip for Creating CIS Benchmark Compliant Clusters
+- You can reverse engineer how to do define a setting in Terraform by changing the setting in Rancher, then going back and checking your Terraform state file to see how it maps to the current state of your infrastructure.## Tip for Creating CIS Benchmark Compliant Clusters
 
 This section describes one way that you can make security and compliance-related config files standard in your clusters.
 

versioned_docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-rke1-templates/infrastructure.md

@@ -50,11 +50,7 @@ When you need to make changes to your infrastructure, instead of manually updati
 
 - You can also modify auth in the Terraform provider.
 
-- You can reverse engineer how to do define a setting in Terraform by changing the setting in Rancher, then going back and checking your Terraform state file to see how it maps to the current state of your infrastructure.
-
-- If you want to manage Kubernetes cluster settings, Rancher settings, and hardware settings all in one place, use [Terraform modules](https://github.com/rancher/terraform-modules). You can pass a cluster configuration YAML file or an RKE template configuration file to a Terraform module so that the Terraform module will create it. In that case, you could use your infrastructure-as-code to manage the version control and revision history of both your Kubernetes cluster and its underlying hardware.
-
-## Tip for Creating CIS Benchmark Compliant Clusters
+- You can reverse engineer how to do define a setting in Terraform by changing the setting in Rancher, then going back and checking your Terraform state file to see how it maps to the current state of your infrastructure.## Tip for Creating CIS Benchmark Compliant Clusters
 
 This section describes one way that you can make security and compliance-related config files standard in your clusters.