metio · sebhoss · Sep 13, 2024 · Sep 13, 2024
diff --git a/...g/CrunchyData/postgres-operator/postgres-operator.crunchydata.com/v1beta1/pgupgrades.yaml b/...g/CrunchyData/postgres-operator/postgres-operator.crunchydata.com/v1beta1/pgupgrades.yaml
@@ -588,7 +588,7 @@ spec:
                   type: "object"
                 fromPostgresVersion:
                   description: "The major version of PostgreSQL before the upgrade."
-                  maximum: 16.0
+                  maximum: 17.0
                   minimum: 10.0
                   type: "integer"
                 image:
@@ -674,7 +674,7 @@ spec:
                   type: "string"
                 toPostgresVersion:
                   description: "The major version of PostgreSQL to be upgraded to."
-                  maximum: 16.0
+                  maximum: 17.0
                   minimum: 10.0
                   type: "integer"
                 tolerations:

diff --git a/...chyData/postgres-operator/postgres-operator.crunchydata.com/v1beta1/postgresclusters.yaml b/...chyData/postgres-operator/postgres-operator.crunchydata.com/v1beta1/postgresclusters.yaml
@@ -6961,7 +6961,7 @@ spec:
                   type: "string"
                 postgresVersion:
                   description: "The major version of PostgreSQL installed in the PostgreSQL image"
-                  maximum: 16.0
+                  maximum: 17.0
                   minimum: 10.0
                   type: "integer"
                 proxy:

diff --git a/...atform/spark-on-k8s-operator/sparkoperator.k8s.io/v1beta2/scheduledsparkapplications.yaml b/...atform/spark-on-k8s-operator/sparkoperator.k8s.io/v1beta2/scheduledsparkapplications.yaml
@@ -2005,6 +2005,9 @@ spec:
                               - "protocol"
                             type: "object"
                           type: "array"
+                        priorityClassName:
+                          description: "PriorityClassName is the name of the PriorityClass for the driver pod."
+                          type: "string"
                         schedulerName:
                           description: "SchedulerName specifies the scheduler that will be used for scheduling"
                           type: "string"
@@ -4980,6 +4983,9 @@ spec:
                               - "protocol"
                             type: "object"
                           type: "array"
+                        priorityClassName:
+                          description: "PriorityClassName is the name of the PriorityClass for the executor pod."
+                          type: "string"
                         schedulerName:
                           description: "SchedulerName specifies the scheduler that will be used for scheduling"
                           type: "string"

diff --git a/...leCloudPlatform/spark-on-k8s-operator/sparkoperator.k8s.io/v1beta2/sparkapplications.yaml b/...leCloudPlatform/spark-on-k8s-operator/sparkoperator.k8s.io/v1beta2/sparkapplications.yaml
@@ -1985,6 +1985,9 @@ spec:
                           - "protocol"
                         type: "object"
                       type: "array"
+                    priorityClassName:
+                      description: "PriorityClassName is the name of the PriorityClass for the driver pod."
+                      type: "string"
                     schedulerName:
                       description: "SchedulerName specifies the scheduler that will be used for scheduling"
                       type: "string"
@@ -4960,6 +4963,9 @@ spec:
                           - "protocol"
                         type: "object"
                       type: "array"
+                    priorityClassName:
+                      description: "PriorityClassName is the name of the PriorityClass for the executor pod."
+                      type: "string"
                     schedulerName:
                       description: "SchedulerName specifies the scheduler that will be used for scheduling"
                       type: "string"

diff --git a/crd-catalog/Kuadrant/dns-operator/kuadrant.io/v1alpha1/dnsrecords.yaml b/crd-catalog/Kuadrant/dns-operator/kuadrant.io/v1alpha1/dnsrecords.yaml
@@ -125,6 +125,9 @@ spec:
                   minLength: 1
                   pattern: "^(?:[\\w\\-.~:\\/?#[\\]@!$&'()*+,;=]+)\\.(?:[\\w\\-.~:\\/?#[\\]@!$&'()*+,;=]+)$"
                   type: "string"
+                  x-kubernetes-validations:
+                    - message: "RootHost is immutable"
+                      rule: "self == oldSelf"
               required:
                 - "providerRef"
                 - "rootHost"
@@ -344,10 +347,6 @@ spec:
                   description: "QueuedAt is a time when DNS record was received for the reconciliation"
                   format: "date-time"
                   type: "string"
-                queuedFor:
-                  description: "QueuedFor is a time when we expect a DNS record to be reconciled again"
-                  format: "date-time"
-                  type: "string"
                 validFor:
                   description: "ValidFor indicates duration since the last reconciliation we consider data in the record to be valid"
                   type: "string"

diff --git a/...alog/aerospike/aerospike-kubernetes-operator/asdb.aerospike.com/v1/aerospikeclusters.yaml b/...alog/aerospike/aerospike-kubernetes-operator/asdb.aerospike.com/v1/aerospikeclusters.yaml
diff --git a/...aerospike/aerospike-kubernetes-operator/asdb.aerospike.com/v1beta1/aerospikeclusters.yaml b/...aerospike/aerospike-kubernetes-operator/asdb.aerospike.com/v1beta1/aerospikeclusters.yaml
diff --git a/crd-catalog/apache/camel-k/camel.apache.org/v1/integrationplatforms.yaml b/crd-catalog/apache/camel-k/camel.apache.org/v1/integrationplatforms.yaml
@@ -695,7 +695,7 @@ spec:
                             - "knative-service"
                           type: "string"
                         useSSA:
-                          description: "Use server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
+                          description: "Deprecated: won't be able to enforce client side update in the future.\nUse server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
                           type: "boolean"
                       type: "object"
                     deployment:
@@ -2286,7 +2286,7 @@ spec:
                             - "knative-service"
                           type: "string"
                         useSSA:
-                          description: "Use server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
+                          description: "Deprecated: won't be able to enforce client side update in the future.\nUse server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
                           type: "boolean"
                       type: "object"
                     deployment:

diff --git a/crd-catalog/apache/camel-k/camel.apache.org/v1/integrationprofiles.yaml b/crd-catalog/apache/camel-k/camel.apache.org/v1/integrationprofiles.yaml
@@ -589,7 +589,7 @@ spec:
                             - "knative-service"
                           type: "string"
                         useSSA:
-                          description: "Use server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
+                          description: "Deprecated: won't be able to enforce client side update in the future.\nUse server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
                           type: "boolean"
                       type: "object"
                     deployment:
@@ -2085,7 +2085,7 @@ spec:
                             - "knative-service"
                           type: "string"
                         useSSA:
-                          description: "Use server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
+                          description: "Deprecated: won't be able to enforce client side update in the future.\nUse server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
                           type: "boolean"
                       type: "object"
                     deployment:

diff --git a/crd-catalog/apache/camel-k/camel.apache.org/v1/integrations.yaml b/crd-catalog/apache/camel-k/camel.apache.org/v1/integrations.yaml
@@ -4213,7 +4213,7 @@ spec:
                             - "knative-service"
                           type: "string"
                         useSSA:
-                          description: "Use server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
+                          description: "Deprecated: won't be able to enforce client side update in the future.\nUse server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
                           type: "boolean"
                       type: "object"
                     deployment:

diff --git a/crd-catalog/apache/camel-k/camel.apache.org/v1/pipes.yaml b/crd-catalog/apache/camel-k/camel.apache.org/v1/pipes.yaml
@@ -4200,7 +4200,7 @@ spec:
                                 - "knative-service"
                               type: "string"
                             useSSA:
-                              description: "Use server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
+                              description: "Deprecated: won't be able to enforce client side update in the future.\nUse server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
                               type: "boolean"
                           type: "object"
                         deployment:

diff --git a/crd-catalog/apache/camel-k/camel.apache.org/v1alpha1/kameletbindings.yaml b/crd-catalog/apache/camel-k/camel.apache.org/v1alpha1/kameletbindings.yaml
@@ -4202,7 +4202,7 @@ spec:
                                 - "knative-service"
                               type: "string"
                             useSSA:
-                              description: "Use server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
+                              description: "Deprecated: won't be able to enforce client side update in the future.\nUse server-side apply to update the owned resources (default `true`).\nNote that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters."
                               type: "boolean"
                           type: "object"
                         deployment:

diff --git a/crd-catalog/apecloud/kubeblocks/apps.kubeblocks.io/v1alpha1/clusterdefinitions.yaml b/crd-catalog/apecloud/kubeblocks/apps.kubeblocks.io/v1alpha1/clusterdefinitions.yaml
@@ -62,7 +62,7 @@ spec:
                           description: "ClusterTopologyComponent defines a Component within a ClusterTopology."
                           properties:
                             compDef:
-                              description: "Specifies the name or prefix of the ComponentDefinition custom resource(CR) that\ndefines the Component's characteristics and behavior.\n\n\nWhen a prefix is used, the system selects the ComponentDefinition CR with the latest version that matches the prefix.\nThis approach allows:\n\n\n1. Precise selection by providing the exact name of a ComponentDefinition CR.\n2. Flexible and automatic selection of the most up-to-date ComponentDefinition CR by specifying a prefix.\n\n\nOnce set, this field cannot be updated."
+                              description: "Specifies the exact name, name prefix, or regular expression pattern for matching the name of the ComponentDefinition\ncustom resource (CR) that defines the Component's characteristics and behavior.\n\n\nThe system selects the ComponentDefinition CR with the latest version that matches the pattern.\nThis approach allows:\n\n\n1. Precise selection by providing the exact name of a ComponentDefinition CR.\n2. Flexible and automatic selection of the most up-to-date ComponentDefinition CR\n\t  by specifying a name prefix or regular expression pattern.\n\n\nOnce set, this field cannot be updated."
                               maxLength: 64
                               type: "string"
                             name:

diff --git a/crd-catalog/apecloud/kubeblocks/apps.kubeblocks.io/v1alpha1/clusters.yaml b/crd-catalog/apecloud/kubeblocks/apps.kubeblocks.io/v1alpha1/clusters.yaml
@@ -176,7 +176,7 @@ spec:
                         description: "Specifies Annotations to override or add for underlying Pods."
                         type: "object"
                       componentDef:
-                        description: "References the name of a ComponentDefinition object.\nThe ComponentDefinition specifies the behavior and characteristics of the Component.\nIf both `componentDefRef` and `componentDef` are provided,\nthe `componentDef` will take precedence over `componentDefRef`."
+                        description: "Specifies the exact name, name prefix, or regular expression pattern for matching the name of the ComponentDefinition\ncustom resource (CR) that defines the Component's characteristics and behavior.\n\n\nIf both `componentDefRef` and `componentDef` are provided,\nthe `componentDef` will take precedence over `componentDefRef`."
                         maxLength: 64
                         pattern: "^[a-z0-9]([a-z0-9\\.\\-]*[a-z0-9])?$"
                         type: "string"
@@ -5207,7 +5207,7 @@ spec:
                             description: "Specifies Annotations to override or add for underlying Pods."
                             type: "object"
                           componentDef:
-                            description: "References the name of a ComponentDefinition object.\nThe ComponentDefinition specifies the behavior and characteristics of the Component.\nIf both `componentDefRef` and `componentDef` are provided,\nthe `componentDef` will take precedence over `componentDefRef`."
+                            description: "Specifies the exact name, name prefix, or regular expression pattern for matching the name of the ComponentDefinition\ncustom resource (CR) that defines the Component's characteristics and behavior.\n\n\nIf both `componentDefRef` and `componentDef` are provided,\nthe `componentDef` will take precedence over `componentDefRef`."
                             maxLength: 64
                             pattern: "^[a-z0-9]([a-z0-9\\.\\-]*[a-z0-9])?$"
                             type: "string"
@@ -9385,7 +9385,7 @@ spec:
                     - "DedicatedNode"
                   type: "string"
                 terminationPolicy:
-                  description: "Specifies the behavior when a Cluster is deleted.\nIt defines how resources, data, and backups associated with a Cluster are managed during termination.\nChoose a policy based on the desired level of resource cleanup and data preservation:\n\n\n- `DoNotTerminate`: Prevents deletion of the Cluster. This policy ensures that all resources remain intact.\n- `Halt`: Deletes Cluster resources like Pods and Services but retains Persistent Volume Claims (PVCs),\n  allowing for data preservation while stopping other operations.\n- `Delete`: Extends the `Halt` policy by also removing PVCs, leading to a thorough cleanup while\n  removing all persistent data.\n- `WipeOut`: An aggressive policy that deletes all Cluster resources, including volume snapshots and\n  backups in external storage.\n  This results in complete data removal and should be used cautiously, primarily in non-production environments\n  to avoid irreversible data loss.\n\n\nWarning: Choosing an inappropriate termination policy can result in data loss.\nThe `WipeOut` policy is particularly risky in production environments due to its irreversible nature."
+                  description: "Specifies the behavior when a Cluster is deleted.\nIt defines how resources, data, and backups associated with a Cluster are managed during termination.\nChoose a policy based on the desired level of resource cleanup and data preservation:\n\n\n- `DoNotTerminate`: Prevents deletion of the Cluster. This policy ensures that all resources remain intact.\n- `Halt`: Deletes Cluster resources like Pods and Services but retains Persistent Volume Claims (PVCs),\n  allowing for data preservation while stopping other operations.\n   Warning: Halt policy is deprecated in 0.9.1 and will have same meaning as DoNotTerminate.\n- `Delete`: Extends the `Halt` policy by also removing PVCs, leading to a thorough cleanup while\n  removing all persistent data.\n- `WipeOut`: An aggressive policy that deletes all Cluster resources, including volume snapshots and\n  backups in external storage.\n  This results in complete data removal and should be used cautiously, primarily in non-production environments\n  to avoid irreversible data loss.\n\n\nWarning: Choosing an inappropriate termination policy can result in data loss.\nThe `WipeOut` policy is particularly risky in production environments due to its irreversible nature."
                   enum:
                     - "DoNotTerminate"
                     - "Halt"