- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for moving (0.15 sec)
-
helm/minio/README.md
only allow pods with the generated client label to connect to MinIO. This label will be displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClaim. First, create the secret: ```bash
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) -
README.md
require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Overview](https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html) for more complete documentation. ### Stable
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Feb 14 17:51:34 GMT 2024 - 18.7K bytes - Viewed (0) -
docs/distributed/README.md
and [bit rot](https://github.com/minio/minio/blob/master/docs/erasure/README.md#what-is-bit-rot-protection) using [erasure code](https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html). As the minimum drives required for distributed MinIO is 2 (same as minimum drives required for erasure coding), erasure code automatically kicks in as you launch distributed MinIO. If one or more drives are offline at the start of a PutObject or NewMultipartUpload operation the object will...
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 8.8K bytes - Viewed (0)