bump: operator-rs 0.52.1

CHANGELOG.md

@@ -13,7 +13,7 @@ All notable changes to this project will be documented in this file.
 ### Changed
 
 - `vector` `0.26.0` -> `0.31.0` ([#361]).
-- `operator-rs` `0.44.0` -> `0.52.0` ([#360], [#376]).
+- `operator-rs` `0.44.0` -> `0.52.1` ([#360], [#376]).
 
 [#360]: https://github.com/stackabletech/hive-operator/pull/360
 [#361]: https://github.com/stackabletech/hive-operator/pull/361

Cargo.toml

@@ -24,7 +24,7 @@ serde = { version = "1.0", features = ["derive"] }
 serde_json = "1.0"
 serde_yaml = "0.9"
 snafu = "0.7"
-stackable-operator = { git = "https://github.com/stackabletech/operator-rs.git", tag = "0.52.0" }
+stackable-operator = { git = "https://github.com/stackabletech/operator-rs.git", tag = "0.52.1" }
 strum = { version = "0.25", features = ["derive"] }
 tokio = { version = "1.29", features = ["full"] }
 tracing = "0.1"

deploy/helm/hive-operator/crds/crds.yaml

@@ -242,12 +242,7 @@ spec:
                       type: string
                   type: object
                 metastore:
-                  description: |-
-                    This struct represents a role - e.g. HDFS datanodes or Trino workers. It has a [`HashMap`] containing all the roleGroups that are part of this role. Additionally, there is a `config`, which is configurable at the role *and* roleGroup level. Everything at roleGroup level is merged on top of what is configured on role level using the [`Merge`] trait. There is also a second form of config, which can only be configured at role level, the `roleConfig`.
-
-                    `T` here is the `config` shared between role and roleGroup.
-
-                    `U` here is the `roleConfig` only available on the role. It defaults to [`GenericRoleConfig`], as this is sufficient for most products. There are some exceptions, where e.g. [`EmptyRoleConfig`] is used. However, product-operators can define their own - custom - struct and use that here.
+                  description: This struct represents a role - e.g. HDFS datanodes or Trino workers. It has a [`HashMap`] containing all the roleGroups that are part of this role. Additionally, there is a `config`, which is configurable at the role *and* roleGroup level. Everything at roleGroup level is merged on top of what is configured on role level using the [`Merge`] trait. There is also a second form of config, which can only be configured at role level, the `roleConfig`.
                   nullable: true
                   properties:
                     cliOverrides:
@@ -3706,15 +3701,13 @@ spec:
                         podDisruptionBudget:
                           enabled: true
                           maxUnavailable: null
-                      description: |-
-                        This is a product-agnostic RoleConfig, which fulfills the needs for most of the product. Currently it contains:
-
-                        1. `podDisruptionBudget` to configure the created PDBs.
+                      description: This is a product-agnostic RoleConfig, which is sufficient for most of the products.
                       properties:
                         podDisruptionBudget:
                           default:
                             enabled: true
                             maxUnavailable: null
+                          description: 'This struct is used to configure: 1.) If PodDisruptionBudgets are created by the operator 2.) The allowed number of Pods to be unavailable (`maxUnavailable`)'
                           properties:
                             enabled:
                               default: true