20260226 doc 16238

src/current/_data/redirects.yml

@@ -1082,5 +1082,22 @@
   sources: ['orchestrate-a-local-cluster-with-kubernetes.md', 'orchestrate-a-local-cluster-with-kubernetes-insecure.md']
   versions: ['v26.1']
 
+- destination: deploy-cockroachdb-on-premises.md
+  sources: ['deploy-cockroachdb-on-premises-insecure.md']
+  versions: ['v26.1']
+
+- destination: deploy-cockroachdb-on-aws.md
+  sources: ['deploy-cockroachdb-on-aws-insecure.md']
+  versions: ['v26.1']
 
+- destination: deploy-cockroachdb-on-microsoft-azure.md
+  sources: ['deploy-cockroachdb-on-microsoft-azure-insecure.md']
+  versions: ['v26.1']
 
+- destination: deploy-cockroachdb-on-google-cloud-platform.md
+  sources: ['deploy-cockroachdb-on-google-cloud-platform-insecure.md']
+  versions: ['v26.1']
+
+- destination: deploy-cockroachdb-on-digital-ocean.md
+  sources: ['deploy-cockroachdb-on-digital-ocean-insecure.md']
+  versions: ['v26.1']

src/current/_includes/v26.1/sidebar-data/self-hosted-deployments.json

@@ -52,36 +52,31 @@
               {
                 "title": "Deploy On-Premises",
                 "urls": [
-                  "/${VERSION}/deploy-cockroachdb-on-premises.html",
-                  "/${VERSION}/deploy-cockroachdb-on-premises-insecure.html"
+                  "/${VERSION}/deploy-cockroachdb-on-premises.html"
                 ]
               },
               {
                 "title": "Deploy on AWS",
                 "urls": [
-                  "/${VERSION}/deploy-cockroachdb-on-aws.html",
-                  "/${VERSION}/deploy-cockroachdb-on-aws-insecure.html"
+                  "/${VERSION}/deploy-cockroachdb-on-aws.html"
                 ]
               },
               {
                 "title": "Deploy on Azure",
                 "urls": [
-                  "/${VERSION}/deploy-cockroachdb-on-microsoft-azure.html",
-                  "/${VERSION}/deploy-cockroachdb-on-microsoft-azure-insecure.html"
+                  "/${VERSION}/deploy-cockroachdb-on-microsoft-azure.html"
                 ]
               },
               {
                 "title": "Deploy on Google Cloud Platform GCE",
                 "urls": [
-                  "/${VERSION}/deploy-cockroachdb-on-google-cloud-platform.html",
-                  "/${VERSION}/deploy-cockroachdb-on-google-cloud-platform-insecure.html"
+                  "/${VERSION}/deploy-cockroachdb-on-google-cloud-platform.html"
                 ]
               },
               {
                 "title": "Deploy on Digital Ocean",
                 "urls": [
-                  "/${VERSION}/deploy-cockroachdb-on-digital-ocean.html",
-                  "/${VERSION}/deploy-cockroachdb-on-digital-ocean-insecure.html"
+                  "/${VERSION}/deploy-cockroachdb-on-digital-ocean.html"
                 ]
               }
             ]

src/current/v26.1/deploy-cockroachdb-on-aws.md

@@ -7,8 +7,6 @@ ssh-link: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html
 docs_area:
 ---
 
-{% include {{ page.version.version }}/filter-tabs/deploy-crdb-aws.md %}
-
 This page shows you how to manually deploy a multi-node, self-hosted CockroachDB cluster on Amazon's AWS EC2 platform, using AWS's managed load-balancing service to distribute client traffic.
 
 After setting up the AWS network, clock synchronization, and load balancing, it should take approximately 20 minutes to complete the deployment. This is based on initializing a three-node CockroachDB cluster in a single AWS region and running our sample workload.

src/current/v26.1/deploy-cockroachdb-on-digital-ocean.md

@@ -7,8 +7,6 @@ ssh-link: https://www.digitalocean.com/community/tutorials/how-to-connect-to-you
 docs_area:
 ---
 
-{% include {{ page.version.version }}/filter-tabs/deploy-crdb-do.md %}
-
 This page shows you how to deploy a secure multi-node CockroachDB cluster on Digital Ocean, using Digital Ocean's managed load balancing service to distribute client traffic.
 
 If you are only testing CockroachDB, or you are not concerned with protecting network communication with TLS encryption, you can use an insecure cluster instead. Select **Insecure** above for instructions.