You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`health-probe-bind-address`|`:8081`| - | no | The address the probe endpoint binds to. Comes from Operator SDK. |
80
-
|`leader-elect`|`false`| - | no | Enable leader election for controller manager. Enabling this will ensure there is only one active controller manager. Comes from Operator SDK. |
81
-
|`metrics-bind-address`|`:8080`| - | no | The address the metric endpoint binds to. Comes from Operator SDK. |
82
-
|`region`|`us-east-1`| - | no | The region to configure for the S3 client. |
83
-
|`s3-access-key`| - |`S3_ACCESS_KEY`| no | The access key used to interact with the S3 server. |
84
-
|`s3-ca-certificate-base64`| - | - | yes | (Optional) Base64 encoded, PEM format CA certificate, for https requests to the S3 server. |
85
-
|`s3-ca-certificate-bundle-path`| - | - | no | (Optional) Path to a CA certificates bundle file, for https requests to the S3 server. |
86
-
|`s3-endpoint-url`|`localhost:9000`| - | no | Hostname (or hostname:port) of the S3 server. |
|`s3-secret-key`| - |`S3_SECRET_KEY`| no | The secret key used to interact with the S3 server. |
89
-
|`useSsl`| true | - | no | Use of SSL/TLS to connect to the S3 server |
90
-
|`bucket-deletion`| false | - | no | Trigger bucket deletion on the S3 backend upon CR deletion. Will fail if bucket is not empty. |
91
-
|`policy-deletion`| false | - | no | Trigger policy deletion on the S3 backend upon CR deletion |
92
-
|`path-deletion`| false | - | no | Trigger path deletion on the S3 backend upon CR deletion. Limited to deleting the `.keep` files used by the operator. |
93
-
|`s3User-deletion`| false | - | no | Trigger S3User deletion on the S3 backend upon CR deletion. |
94
-
|`override-existing-secret`| false | - | no | Update secret linked to s3User if already exist, else noop |
95
-
|`s3LabelSelector`| "" | - | no | Filter resource that this instance will manage. If Empty all resource in the cluster will be manage |
77
+
| Flag name | Default | Environment variable | Multiple values allowed | Description |
|`health-probe-bind-address`|`:8081`| - | no | The address the probe endpoint binds to. Comes from Operator SDK. |
80
+
|`leader-elect`|`false`| - | no | Enable leader election for controller manager. Enabling this will ensure there is only one active controller manager. Comes from Operator SDK. |
81
+
|`metrics-bind-address`|`:8080`| - | no | The address the metric endpoint binds to. Comes from Operator SDK. ||
82
+
|`override-existing-secret`| false | - | no | Update secret linked to s3User if already exist, else noop |
96
83
## Minimal rights needed to work
97
84
98
85
The Operator need at least this rights:
@@ -166,10 +153,15 @@ metadata:
166
153
name: s3-default-instance # Name of the S3Instance
167
154
spec:
168
155
s3Provider: minio # Type of the Provider. Can be "mockedS3Provider" or "minio"
169
-
urlEndpoint: minio.example.com # URL of the Provider
170
-
secretName: minio-credentials # Name of the secret containing 2 Keys S3_ACCESS_KEY and S3_SECRET_KEY
156
+
url: https://minio.example.com # URL of the Provider
157
+
secretRef: minio-credentials # Name of the secret containing 2 Keys S3_ACCESS_KEY and S3_SECRET_KEY
158
+
caCertSecretRef: minio-certs # Name of the secret containing key ca.crt with cert of s3provider
171
159
region: us-east-1 # Region of the Provider
172
-
useSSL: true # useSSL to query the Provider
160
+
allowedNamespaces: [] # namespaces allowed to have buckets, policies, ... Wildcard prefix/suffix allowed. If empty only the same namespace as s3instance is allowed
161
+
bucketDeletionEnabled: true # Allowed bucket entity suppression on s3instance
162
+
policyDeletionEnabled: true # Allowed policy entity suppression on s3instance
163
+
pathDeletionEnabled: true # Allowed path entity suppression on s3instance
164
+
s3UserDeletionEnabled: true # Allowed s3User entity suppression on s3instance
173
165
```
174
166
175
167
### Bucket example
@@ -307,6 +299,13 @@ spec:
307
299
308
300
Each S3user is linked to a kubernetes secret which have the same name that the S3User. The secret contains 2 keys: `accessKey` and `secretKey`.
309
301
302
+
### :info: How works s3InstanceRef
303
+
304
+
S3InstanceRef can get the following values:
305
+
- empty: In this case the s3instance use will be the default one configured at startup if the namespace is in the namespace allowed for this s3Instance
306
+
-`s3InstanceName`: In this case the s3Instance use will be the s3Instance with the name `s3InstanceName` in the current namespace (if the current namespace is allowed)
307
+
-`namespace/s3InstanceName`: In this case the s3Instance use will be the s3Instance with the name `s3InstanceName` in the namespace `namespace` (if the current namespace is allowed to use this s3Instance)
0 commit comments