Add cross-references to new operator content

Author: jhlodin

src/current/_includes/v25.2/cockroachdb-operator-recommendation.md

@@ -0,0 +1,5 @@
+{{site.data.alerts.callout_success}}
+The CockroachDB operator is a fully-featured Kubernetes operator that is designed for ease of deployment and scaling of multi-region clusters. To learn more, read the [CockroachDB operator documentation]({% link {{page.version.version}}/kubernetes-operator-overview.md %}).
+
+New deployments of CockroachDB on Kubernetes are recommended to use the CockroachDB operator. To migrate an existing deployment to use the CockroachDB operator, read the [Helm]({% link {{page.version.version}}/migrate-cockroachdb-kubernetes-helm.md %}) and [public operator]({% link {{page.version.version}}/migrate-cockroachdb-kubernetes-operator.md %}) migration guides.
+{{site.data.alerts.end}}

src/current/v25.2/configure-cockroachdb-kubernetes.md

@@ -9,13 +9,17 @@ docs_area: deploy
 
 {% capture latest_operator_version %}{% include_cached latest_operator_version.md %}{% endcapture %}
 
-This page explains how to configure Kubernetes cluster resources such as memory, CPU, and storage. 
+This page explains how to configure Kubernetes cluster resources such as memory, CPU, and storage.
+
+This page is for Kubernetes deployments that are not using the CockroachDB operator. For guidance specific to the CockroachDB operator, read [Resource management with the CockroachDB operator]({% link {{ page.version.version }}/configure-cockroachdb-kubernetes-operator.md %}).
+
+{% include {{ page.version.version }}/cockroachdb-operator-recommendation.md %}
 
 These settings override the defaults used when [deploying CockroachDB on Kubernetes]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}).
 
 <div class="filters filters-big clearfix">
-    <button class="filter-button" data-scope="operator">Operator</button>
-    <button class="filter-button" data-scope="manual">Manual Configs</button>
+    <button class="filter-button" data-scope="operator">Public operator</button>
+    <button class="filter-button" data-scope="manual">Manual configs</button>
     <button class="filter-button" data-scope="helm">Helm</button>
 </div>
 

src/current/v25.2/deploy-cockroachdb-with-kubernetes-openshift.md

@@ -8,6 +8,8 @@ docs_area:
 
 This page shows you how to start and stop a secure 3-node CockroachDB cluster on the Red Hat OpenShift platform, using the [CockroachDB Kubernetes Operator](https://marketplace.redhat.com/en-us/products/cockroachdb-operator).
 
+{% include {{ page.version.version }}/cockroachdb-operator-recommendation.md %}
+
 ## Before you begin
 
 You must have the following set up before proceeding with this tutorial:

src/current/v25.2/deploy-cockroachdb-with-kubernetes.md

@@ -9,9 +9,11 @@ docs_area:
 
 {% include {{ page.version.version }}/filter-tabs/crdb-single-kubernetes.md %}
 
-This page shows you how to start and stop a secure 3-node CockroachDB cluster in a single [Kubernetes](http://kubernetes.io/) cluster. You can use any of the following approaches:
+{% include {{ page.version.version }}/cockroachdb-operator-recommendation.md %}
 
-- [Public Kubernetes operator](https://github.com/cockroachdb/cockroach-operator)
+This page shows you how to start and stop a secure 3-node CockroachDB cluster in a single [Kubernetes](http://kubernetes.io/) cluster using the following approaches:
+
+- [Public operator](https://github.com/cockroachdb/cockroach-operator)
 
     {{site.data.alerts.callout_info}}
     The CockroachDB Kubernetes Operator is also available on platforms such as [Red Hat OpenShift]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes-openshift.md %}) and [IBM Cloud Pak for Data](https://www.ibm.com/products/cloud-pak-for-data).

src/current/v25.2/kubernetes-overview.md

@@ -10,12 +10,14 @@ key: operate-cockroachdb-kubernetes.html
 
 Kubernetes is a portable, extensible, open source platform for managing containerized workloads and services. For a given workload, you provide Kubernetes with a configuration, and Kubernetes applies that configuration to all Kubernetes nodes that are running the application.
 
-CockroachDB can be deployed and managed on Kubernetes using the following methods:
+{% include {{ page.version.version }}/cockroachdb-operator-recommendation.md %}
 
-- [CockroachDB Kubernetes Operator](https://github.com/cockroachdb/cockroach-operator)
+You can also deploy CockroachDB on Kubernetes using the following methods:
+
+- [Public operator](https://github.com/cockroachdb/cockroach-operator)
 
     {{site.data.alerts.callout_info}}
-    The CockroachDB Kubernetes Operator is also available on platforms such as [Red Hat OpenShift]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes-openshift.md %}) and [IBM Cloud Pak for Data](https://www.ibm.com/products/cloud-pak-for-data).
+    The public operator is also available on platforms such as [Red Hat OpenShift]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes-openshift.md %}) and [IBM Cloud Pak for Data](https://www.ibm.com/products/cloud-pak-for-data).
     {{site.data.alerts.end}}
 
 - Manual [StatefulSet](http://kubernetes.io/docs/concepts/abstractions/controllers/statefulsets/) configuration

src/current/v25.2/kubernetes-performance.md

@@ -7,6 +7,10 @@ docs_area: deploy
 
 Kubernetes provides many useful abstractions for deploying and operating distributed systems, but some of the abstractions come with a performance overhead and an increase in underlying system complexity. This page explains potential bottlenecks to be aware of when [running CockroachDB in Kubernetes]({% link {{ page.version.version }}/kubernetes-overview.md %}) and shows you how to optimize your deployment for better performance.
 
+This page is for Kubernetes deployments that are not using the CockroachDB operator. For guidance specific to the CockroachDB operator, read [CockroachDB Performance on Kubernetes with the CockroachDB Operator]({% link {{ page.version.version }}/kubernetes-operator-performance.md %}).
+
+{% include {{ page.version.version }}/cockroachdb-operator-recommendation.md %}
+
 <div id="toc"></div>
 
 ## Before you begin

src/current/v25.2/monitor-cockroachdb-kubernetes.md

@@ -12,6 +12,10 @@ This article assumes you have already [deployed CockroachDB on a single Kubernet
 
 Despite CockroachDB's various [built-in safeguards against failure]({% link {{ page.version.version }}/architecture/replication-layer.md %}), it is critical to actively monitor the overall health and performance of a cluster running in production and to create alerting rules that promptly send notifications when there are events that require investigation or intervention.
 
+This page is for Kubernetes deployments that are not using the CockroachDB operator. For guidance specific to the CockroachDB operator, read [Cluster Monitoring with the CockroachDB Operator]({% link {{ page.version.version }}/monitor-cockroachdb-kubernetes-operator.md %}).
+
+{% include {{ page.version.version }}/cockroachdb-operator-recommendation.md %}
+
 <div class="filters filters-big clearfix">
     <button class="filter-button" data-scope="operator">Use Operator</button>
     <button class="filter-button" data-scope="manual">Use Configs</button>

src/current/v25.2/orchestrate-cockroachdb-with-kubernetes-multi-cluster.md

@@ -15,9 +15,9 @@ docs_area: deploy
 
 This page shows you how to orchestrate a secure CockroachDB deployment across three [Kubernetes](http://kubernetes.io/) clusters, each in a different geographic region, using [StatefulSets](http://kubernetes.io/docs/concepts/abstractions/controllers/statefulsets/) to manage the containers within each cluster and linking them together via DNS. This will result in a single, multi-region CockroachDB cluster running on Kubernetes.
 
-{{site.data.alerts.callout_success}}
+{% include {{ page.version.version }}/cockroachdb-operator-recommendation.md %}
+
 To deploy CockroachDB in a single Kubernetes cluster instead, see [Kubernetes Single-Cluster Deployment]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}). Also, for details about potential performance bottlenecks to be aware of when running CockroachDB in Kubernetes and guidance on how to optimize your deployment for better performance, see [CockroachDB Performance on Kubernetes]({% link {{ page.version.version }}/kubernetes-performance.md %}).
-{{site.data.alerts.end}}
 
 ## Before you begin
 

src/current/v25.2/scale-cockroachdb-kubernetes.md

@@ -13,8 +13,12 @@ This article assumes you have already [deployed CockroachDB on a single Kubernet
 
 This page explains how to add and remove CockroachDB nodes on Kubernetes.
 
+This page is for Kubernetes deployments that are not using the CockroachDB operator. For guidance specific to the CockroachDB operator, read [Cluster Scaling with the CockroachDB Operator]({% link {{ page.version.version }}/scale-cockroachdb-kubernetes-operator.md %}).
+
+{% include {{ page.version.version }}/cockroachdb-operator-recommendation.md %}
+
 <div class="filters filters-big clearfix">
-    <button class="filter-button" data-scope="operator">Operator</button>
+    <button class="filter-button" data-scope="operator">Public operator</button>
     <button class="filter-button" data-scope="manual">Manual Configs</button>
     <button class="filter-button" data-scope="helm">Helm</button>
 </div>

src/current/v25.2/schedule-cockroachdb-kubernetes.md

@@ -7,15 +7,25 @@ secure: true
 docs_area: deploy
 ---
 
-This page describes how to configure the following, using the [Operator](https://github.com/cockroachdb/cockroach-operator):
+This page describes how to configure the following, using the [public operator](https://github.com/cockroachdb/cockroach-operator):
 
+- [Enable feature gates](#enable-feature-gates)
 - [Node selectors](#node-selectors)
-- [Node affinities](#add-a-node-affinity)
-- [Pod affinities and anti-affinities](#add-a-pod-affinity-or-anti-affinity)
+- [Affinities and anti-affinities](#affinities-and-anti-affinities)
+  - [Add a node affinity](#add-a-node-affinity)
+  - [Add a pod affinity or anti-affinity](#add-a-pod-affinity-or-anti-affinity)
+  - [Example: Scheduling CockroachDB onto labeled nodes](#example-scheduling-cockroachdb-onto-labeled-nodes)
 - [Taints and tolerations](#taints-and-tolerations)
+  - [Add a toleration](#add-a-toleration)
+  - [Example: Evicting CockroachDB from a running worker node](#example-evicting-cockroachdb-from-a-running-worker-node)
 - [Topology spread constraints](#topology-spread-constraints)
+  - [Add a topology spread constraint](#add-a-topology-spread-constraint)
 - [Resource labels and annotations](#resource-labels-and-annotations)
 
+This page is for Kubernetes deployments that are not using the CockroachDB operator. For guidance specific to the CockroachDB operator, read [Pod Scheduling with the CockroachDB Operator]({% link {{ page.version.version }}/schedule-cockroachdb-kubernetes-operator.md %}).
+
+{% include {{ page.version.version }}/cockroachdb-operator-recommendation.md %}
+
 These settings control how CockroachDB pods can be identified or scheduled onto worker nodes.
 
 {% include {{ page.version.version }}/orchestration/operator-check-namespace.md %}