chore: Bump stackable-operator (#335)

* chore: Bump stackable-operator

* chore: Update changelog

* chore: Bump ring transitive dependency

Author: NickLarsenNZ

CHANGELOG.md

@@ -11,7 +11,7 @@ All notable changes to this project will be documented in this file.
 ### Added
 
 - Aggregate emitted Kubernetes events on the CustomResources ([#318]).
-- Add the region field to the S3Connection CRD ([#331]).
+- Add the region field to the S3Connection CRD ([#331], [#335]).
 
 ### Changed
 
@@ -23,6 +23,7 @@ All notable changes to this project will be documented in this file.
 [#321]: https://github.com/stackabletech/commons-operator/pull/321
 [#331]: https://github.com/stackabletech/commons-operator/pull/331
 [#334]: https://github.com/stackabletech/commons-operator/pull/334
+[#335]: https://github.com/stackabletech/commons-operator/pull/335
 
 ## [24.11.1] - 2025-01-09
 

Cargo.lock

@@ -17,7 +17,7 @@ futures = { version = "0.3", features = ["compat"] }
 serde = { version = "1.0", features = ["derive"] }
 serde_json = "1.0"
 snafu = "0.8"
-stackable-operator = { git = "https://github.com/stackabletech/operator-rs.git", tag = "stackable-operator-0.87.0" }
+stackable-operator = { git = "https://github.com/stackabletech/operator-rs.git", tag = "stackable-operator-0.87.2" }
 strum = { version = "0.27", features = ["derive"] }
 tokio = { version = "1.40", features = ["full"] }
 tracing = "0.1"

Cargo.nix

@@ -370,26 +370,14 @@ spec:
                   default:
                     name: us-east-1
                   description: |-
-                    AWS service API region used by the AWS SDK when using AWS S3 buckets.
+                    Bucket region used for signing headers (sigv4).
 
-                    This defaults to `us-east-1` and can be ignored if not using AWS S3 buckets.
+                    This defaults to `us-east-1` which is compatible with other implementations such as Minio.
 
-                    NOTE: This is not the bucket region, and is used by the AWS SDK to construct endpoints for various AWS service APIs. It is only useful when using AWS S3 buckets.
-
-                    When using AWS S3 buckets, you can configure optimal AWS service API connections in the following ways: - From **inside** AWS: Use an auto-discovery source (eg: AWS IMDS). - From **outside** AWS, or when IMDS is disabled, explicity set the region name nearest to where the client application is running from.
-                  oneOf:
-                    - required:
-                        - source
-                    - required:
-                        - name
+                    WARNING: Some products use the Hadoop S3 implementation which falls back to us-east-2.
                   properties:
                     name:
-                      description: 'An explicit region, eg: eu-central-1'
-                      type: string
-                    source:
-                      description: Defer region detection to an auto-discovery mechanism.
-                      enum:
-                        - AwsImds
+                      default: us-east-1
                       type: string
                   type: object
                 tls:
@@ -537,26 +525,14 @@ spec:
                           default:
                             name: us-east-1
                           description: |-
-                            AWS service API region used by the AWS SDK when using AWS S3 buckets.
-
-                            This defaults to `us-east-1` and can be ignored if not using AWS S3 buckets.
+                            Bucket region used for signing headers (sigv4).
 
-                            NOTE: This is not the bucket region, and is used by the AWS SDK to construct endpoints for various AWS service APIs. It is only useful when using AWS S3 buckets.
+                            This defaults to `us-east-1` which is compatible with other implementations such as Minio.
 
-                            When using AWS S3 buckets, you can configure optimal AWS service API connections in the following ways: - From **inside** AWS: Use an auto-discovery source (eg: AWS IMDS). - From **outside** AWS, or when IMDS is disabled, explicity set the region name nearest to where the client application is running from.
-                          oneOf:
-                            - required:
-                                - source
-                            - required:
-                                - name
+                            WARNING: Some products use the Hadoop S3 implementation which falls back to us-east-2.
                           properties:
                             name:
-                              description: 'An explicit region, eg: eu-central-1'
-                              type: string
-                            source:
-                              description: Defer region detection to an auto-discovery mechanism.
-                              enum:
-                                - AwsImds
+                              default: us-east-1
                               type: string
                           type: object
                         tls: