Pritesh feedback

Author: jhlodin

src/current/v26.1/cockroachdb-operator-performance.md

@@ -277,26 +277,26 @@ cockroachdb:
     podTemplate:
       spec:
         affinity:
-        podAntiAffinity:
-            preferredDuringSchedulingIgnoredDuringExecution:
-            - weight: 100
-              podAffinityTerm:
-                labelSelector:
-                  matchExpressions:
-                  - key: app
-                    operator: In
-                    values:
-                    - loadgen
-                topologyKey: kubernetes.io/hostname
-            - weight: 99
-              podAffinityTerm:
-                labelSelector:
-                  matchExpressions:
-                  - key: app
-                    operator: In
-                    values:
-                    - cockroachdb
-                topologyKey: kubernetes.io/hostname
+          podAntiAffinity:
+              preferredDuringSchedulingIgnoredDuringExecution:
+              - weight: 100
+                podAffinityTerm:
+                  labelSelector:
+                    matchExpressions:
+                    - key: app
+                      operator: In
+                      values:
+                      - loadgen
+                  topologyKey: kubernetes.io/hostname
+              - weight: 99
+                podAffinityTerm:
+                  labelSelector:
+                    matchExpressions:
+                    - key: app
+                      operator: In
+                      values:
+                      - cockroachdb
+                  topologyKey: kubernetes.io/hostname
 ~~~
 
 The preceding configuration will first prefer to put the `loadgen` pods on different nodes from each other, which is important for the fault tolerance of the `loadgen` pods themselves. As a secondary priority, it will attempt to put the pods on nodes that do not already have a running `CockroachDB` pod. This will ensure the best possible balance of fault tolerance and performance for the load generator and CockroachDB cluster.

src/current/v26.1/schedule-cockroachdb-operator.md

@@ -365,17 +365,17 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
 
 To assist in working with your cluster, you can add labels and annotations to your resources.
 
-Specify labels in `cockroachdb.crdbCluster.podTemplate.spec.podLabels` and annotations in `cockroachdb.crdbCluster.podTemplate.spec.podAnnotations` in the values file used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-cockroachdb-operator.md %}#initialize-the-cluster):
+Specify labels in `cockroachdb.crdbCluster.podTemplate.metadata.labels` and annotations in `cockroachdb.crdbCluster.podTemplate.metadata.annotations` in the values file used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-cockroachdb-operator.md %}#initialize-the-cluster):
 
 ~~~ yaml
 cockroachdb:
   crdbCluster:
     podTemplate:
-      spec:
-        podLabels:
-          app.kubernetes.io/version: v25.1.4
-        podAnnotations
-          operator: https://raw.githubusercontent.com/cockroachdb/helm-charts/refs/heads/master/cockroachdb-parent/charts/cockroachdb/values.yaml
+      metadata:
+        labels:
+          app.kubernetes.io/name: "cockroachdb"
+        annotations
+          kubernetes.io/description: "This is a CockroachDB pod."
 ~~~
 
 To verify that the labels and annotations were applied to a pod, for example, run `kubectl describe pod {pod-name}`.