auto-update crds catalog

postgresql.cnpg.io/cluster_v1.json

@@ -1385,7 +1385,7 @@
                       "type": "string"
                     },
                     "exclusive": {
-                      "description": "Set the target to be exclusive (defaults to true)",
+                      "description": "Set the target to be exclusive. If omitted, defaults to false, so that in Postgres, `recovery_target_inclusive` will be true",
                       "type": "boolean"
                     },
                     "targetImmediate": {
@@ -2591,6 +2591,10 @@
           ],
           "type": "string"
         },
+        "priorityClassName": {
+          "description": "Name of the priority class which will be used in every generated Pod, if the PriorityClass specified does not exist, the pod will not be able to schedule.  Please refer to https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass for more information",
+          "type": "string"
+        },
         "projectedVolumeTemplate": {
           "description": "Template to be used to define projected volumes, projected volumes will be mounted under `/projected` base folder",
           "properties": {
@@ -3907,6 +3911,11 @@
               "description": "Instances contains the pod topology of the instances",
               "type": "object"
             },
+            "nodesUsed": {
+              "description": "NodesUsed represents the count of distinct nodes accommodating the instances. A value of '1' suggests that all instances are hosted on a single node, implying the absence of High Availability (HA). Ideally, this value should be the same as the number of instances in the Postgres HA cluster, implying shared nothing architecture on the compute side.",
+              "format": "int32",
+              "type": "integer"
+            },
             "successfullyExtracted": {
               "description": "SuccessfullyExtracted indicates if the topology data was extract. It is useful to enact fallback behaviors in synchronous replica election in case of failures",
               "type": "boolean"