- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 105 for specifying (0.15 sec)
-
helm/minio/README.md
First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret:
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Jan 24 07:27:57 GMT 2024 - 10.9K bytes - Viewed (0) -
docs/bucket/retention/README.md
``` See <https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock-overview.html> for AWS S3 spec on object locking and permissions required for specifying legal hold. ## Concepts - If an object is under legal hold, it cannot be deleted unless the legal hold is explicitly removed for the respective version id. DeleteObjectVersion() would fail otherwise.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 3.9K bytes - Viewed (0) -
docs/sts/web-identity.md
## Specifying Access Control with IAM Policies
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 19.2K bytes - Viewed (1) -
cmd/api-errors.go
ErrMissingSSECustomerKey: { Code: "InvalidArgument", Description: "Requests specifying Server Side Encryption with Customer provided keys must provide an appropriate secret key.", HTTPStatusCode: http.StatusBadRequest, }, ErrMissingSSECustomerKeyMD5: { Code: "InvalidArgument",
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun May 05 16:56:21 GMT 2024 - 91.4K bytes - Viewed (7) -
helm-releases/minio-5.0.5.tgz
preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.\<key\> in Secret | Corresponding variable | Description | Required | |:--------...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Feb 03 20:54:02 GMT 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-5.0.7.tgz
preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.\<key\> in Secret | Corresponding variable | Description | Required | |:--------...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Feb 13 10:37:23 GMT 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-3.6.6.tgz
preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.\<key\> in Secret | Corresponding variable | Description | Required | |:--------...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun Apr 17 21:46:44 GMT 2022 - 18.2K bytes - Viewed (0) -
helm-releases/minio-4.0.0.tgz
preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.\<key\> in Secret | Corresponding variable | Description | Required | |:--------...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Apr 26 02:41:39 GMT 2022 - 18K bytes - Viewed (0) -
helm-releases/minio-3.6.1.tgz
preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.\<key\> in Secret | Corresponding variable | Description | Required | |:--------...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Mar 15 00:13:17 GMT 2022 - 17.9K bytes - Viewed (0) -
helm-releases/minio-2.0.0.tgz
preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.<key> in Secret | Corresponding variable | Description | Required | |:--------...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Aug 26 07:36:46 GMT 2021 - 13.6K bytes - Viewed (0)