Upgrade CRD reference

k8ssandra · Jan 15, 2025 · 16f16b8 · 16f16b8
1 parent a6352fc
commit 16f16b8
Showing 1 changed file with 32 additions and 4 deletions.
diff --git a/docs/content/en/reference/crd/k8ssandra-operator-crds-latest/_index.md b/docs/content/en/reference/crd/k8ssandra-operator-crds-latest/_index.md
@@ -1140,8 +1140,7 @@ Example:
         <td><b>datacenterName</b></td>
         <td>string</td>
         <td>
-          DatacenterName allows to override the name of the Cassandra datacenter. Kubernetes objects will be named after a sanitized version of it if set, and if not metadata.name. In Cassandra the DC name will be overridden by this value.
-It may generate some confusion as objects created for the DC will have a different name than the CasandraDatacenter object itself.
+          DatacenterName allows to override the name of the Cassandra datacenter. In Cassandra the DC name will be overridden by this value.
 This setting can create conflicts if multiple DCs coexist in the same namespace if metadata.name for a DC with no override is set to the same value as the override name of another DC.
 Use cautiously.<br/>
         </td>
@@ -1233,6 +1232,13 @@ The default is "mikefarah/yq:4".<br/>
             <i>Default</i>: mikefarah/yq:4<br/>
         </td>
         <td>false</td>
+      </tr><tr>
+        <td><b>podPriorityClassName</b></td>
+        <td>string</td>
+        <td>
+          PodPriorityClassName defines the priority class name for the Cassandra pods.<br/>
+        </td>
+        <td>false</td>
       </tr><tr>
         <td><b><a href="#k8ssandraclusterspeccassandrapodsecuritycontext">podSecurityContext</a></b></td>
         <td>object</td>
@@ -5405,8 +5411,7 @@ Example:
         <td><b>datacenterName</b></td>
         <td>string</td>
         <td>
-          DatacenterName allows to override the name of the Cassandra datacenter. Kubernetes objects will be named after a sanitized version of it if set, and if not metadata.name. In Cassandra the DC name will be overridden by this value.
-It may generate some confusion as objects created for the DC will have a different name than the CasandraDatacenter object itself.
+          DatacenterName allows to override the name of the Cassandra datacenter. In Cassandra the DC name will be overridden by this value.
 This setting can create conflicts if multiple DCs coexist in the same namespace if metadata.name for a DC with no override is set to the same value as the override name of another DC.
 Use cautiously.<br/>
         </td>
@@ -5511,6 +5516,13 @@ started, the per-node ConfigMap is mounted and the contents of each entry corres
 the pod are merged into their respective configuration files.<br/>
         </td>
         <td>false</td>
+      </tr><tr>
+        <td><b>podPriorityClassName</b></td>
+        <td>string</td>
+        <td>
+          PodPriorityClassName defines the priority class name for the Cassandra pods.<br/>
+        </td>
+        <td>false</td>
       </tr><tr>
         <td><b><a href="#k8ssandraclusterspeccassandradatacentersindexpodsecuritycontext">podSecurityContext</a></b></td>
         <td>object</td>
@@ -63692,6 +63704,13 @@ K8ssandraStatus defines the observed of a k8ssandra instance
           CassandraDatacenterStatus defines the observed state of CassandraDatacenter<br/>
         </td>
         <td>false</td>
+      </tr><tr>
+        <td><b>contextName</b></td>
+        <td>string</td>
+        <td>
+          <br/>
+        </td>
+        <td>false</td>
       </tr><tr>
         <td><b>decommissionProgress</b></td>
         <td>string</td>
@@ -63774,6 +63793,15 @@ with the management API<br/>
             <i>Format</i>: date-time<br/>
         </td>
         <td>false</td>
+      </tr><tr>
+        <td><b>metadataVersion</b></td>
+        <td>integer</td>
+        <td>
+          <br/>
+          <br/>
+            <i>Format</i>: int64<br/>
+        </td>
+        <td>false</td>
       </tr><tr>
         <td><b>nodeReplacements</b></td>
         <td>[]string</td>