Remove hardcoded uid and gid, they'll default to the ones from the docker images now

Author: lfrancke

CHANGELOG.md

@@ -20,6 +20,8 @@
 - BREAKING: Inject the vector aggregator address into the vector config using the env var `VECTOR_AGGREGATOR_ADDRESS` instead
     of having the operator write it to the vector config ([#645]).
 - test: Bump to Vector `0.46.1` ([#657]).
+- Previously this operator would hardcode the UID and GID of the Pods being created to 1000/0, this has changed now ([#660])
+  - The defaults from the docker images itself will now apply, which will be different from 1000/0 going forward
 
 ### Fixed
 
@@ -39,6 +41,7 @@
 [#654]: https://github.com/stackabletech/hbase-operator/pull/654
 [#655]: https://github.com/stackabletech/hbase-operator/pull/655
 [#657]: https://github.com/stackabletech/hbase-operator/pull/657
+[#660]: https://github.com/stackabletech/hbase-operator/pull/660
 
 ## [25.3.0] - 2025-03-21
 

rust/operator-binary/src/hbase_controller.rs

@@ -101,7 +101,6 @@ const HBASE_CONFIG_TMP_DIR: &str = "/stackable/tmp/hbase";
 const HBASE_LOG_CONFIG_TMP_DIR: &str = "/stackable/tmp/log_config";
 
 const DOCKER_IMAGE_BASE_NAME: &str = "hbase";
-const HBASE_UID: i64 = 1000;
 
 pub struct Ctx {
     pub client: stackable_operator::client::Client,
@@ -939,13 +938,7 @@ fn build_rolegroup_statefulset(
         )
         .context(AddVolumeSnafu)?
         .service_account_name(service_account.name_any())
-        .security_context(
-            PodSecurityContextBuilder::new()
-                .run_as_user(HBASE_UID)
-                .run_as_group(0)
-                .fs_group(1000)
-                .build(),
-        );
+        .security_context(PodSecurityContextBuilder::new().fs_group(1000).build());
 
     if let Some(ContainerLogConfig {
         choice: