fix: remove v2 references in comments

Author: maltesander

rust/operator-binary/src/controller.rs

@@ -50,7 +50,7 @@ pub(crate) mod dereference;
 pub(crate) mod node_id_hasher;
 pub(crate) mod validate;
 
-/// The type-safe role-group name from stackable-operator's v2 module. Re-exported so the rest
+/// The type-safe role-group name from stackable-operator. Re-exported so the rest
 /// of the operator can refer to it as `controller::RoleGroupName`.
 pub use stackable_operator::v2::types::operator::{RoleGroupName, RoleName};
 
@@ -101,7 +101,6 @@ pub enum PodDescriptorsError {
 /// The cluster identity (`name`, `namespace`, `uid`) is captured here so that owner
 /// references for child objects can be built straight from this struct (via its
 /// [`Resource`] impl) without threading the raw [`v1alpha1::KafkaCluster`] around.
-/// This mirrors the hive-/opensearch-operator's `ValidatedCluster`.
 pub struct ValidatedCluster {
     /// `ObjectMeta` carrying `name`, `namespace` and `uid`, so this struct can act as the
     /// owner [`Resource`] for child objects.

rust/operator-binary/src/controller/build/properties/product_logging/mod.rs

@@ -26,7 +26,7 @@ const KAFKA_LOG4J2_FILE: &str = "kafka.log4j2.xml";
 
 /// The static, env-driven Vector agent configuration (`vector.yaml`).
 ///
-/// The v2 [`vector_container`](stackable_operator::v2::product_logging::framework::vector_container)
+/// The [`vector_container`](stackable_operator::v2::product_logging::framework::vector_container)
 /// mounts this file and supplies its `${...}` values (`LOG_DIR`, `DATA_DIR`, `NAMESPACE`,
 /// `CLUSTER_NAME`, `ROLE_NAME`, `ROLE_GROUP_NAME`, `VECTOR_AGGREGATOR_ADDRESS`) as env vars.
 const VECTOR_CONFIG: &str = include_str!("vector.yaml");

rust/operator-binary/src/controller/build/resource/rbac.rs

@@ -1,6 +1,6 @@
 //! Builds the cluster-wide RBAC resources (`ServiceAccount` and `RoleBinding`).
 //!
-//! The names come from the v2 [`ResourceNames`](stackable_operator::v2::role_utils::ResourceNames)
+//! The names come from [`ResourceNames`](stackable_operator::v2::role_utils::ResourceNames)
 //! and are identical to the previously used `commons::rbac::build_rbac_resources`
 //! (`<cluster>-serviceaccount`, `<cluster>-rolebinding`, `<product>-clusterrole`), so switching to
 //! this builder does not rename any RBAC objects.

rust/operator-binary/src/controller/build/resource/statefulset.rs

@@ -765,12 +765,12 @@ fn add_common_pod_config(
     Ok(())
 }
 
-/// Adds the v2 Vector log-aggregation sidecar container, when the Vector agent is enabled.
+/// Adds the Vector log-aggregation sidecar container, when the Vector agent is enabled.
 ///
 /// Whether Vector is enabled, the per-container log config and the (validated) aggregator
 /// discovery `ConfigMap` name are resolved up-front in
 /// [`ValidatedLogging`](crate::controller::validate::ValidatedLogging). The container mounts the
-/// static `vector.yaml` from the `config` volume and is driven by the env vars the v2
+/// static `vector.yaml` from the `config` volume and is driven by the env vars the
 /// [`vector_container`] sets.
 fn add_vector_container(
     pod_builder: &mut PodBuilder,

rust/operator-binary/src/controller/validate.rs

@@ -110,9 +110,9 @@ pub enum Error {
 /// Validated logging configuration for a Kafka role group's Kafka and (optional) Vector
 /// containers.
 ///
-/// Produced up-front by [`validate_logging`] (mirroring the hive-/opensearch-operator) so that
-/// an invalid custom log `ConfigMap` name or a missing Vector aggregator discovery `ConfigMap`
-/// name fails reconciliation during validation rather than at resource-build time.
+/// Produced up-front by [`validate_logging`] so that an invalid custom log `ConfigMap` name or a
+/// missing Vector aggregator discovery `ConfigMap` name fails reconciliation during validation
+/// rather than at resource-build time.
 #[derive(Clone, Debug, PartialEq)]
 pub struct ValidatedLogging {
     pub kafka_container: ValidatedContainerLogConfigChoice,