- Sort Score
- Num 10 results
- Language All
Results 391 - 400 of 437 for stacking (0.05 seconds)
-
helm-releases/minio-3.4.8.tgz
fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Jan 28 18:33:38 GMT 2022 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.5.2.tgz
fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Feb 08 00:29:26 GMT 2022 - 15.4K bytes - Click Count (0) -
helm-releases/minio-3.1.8.tgz
fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Oct 07 05:03:47 GMT 2021 - 14.6K bytes - Click Count (0) -
helm-releases/minio-3.2.0.tgz
fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Oct 13 02:16:24 GMT 2021 - 14.6K bytes - Click Count (0) -
helm-releases/minio-3.3.3.tgz
fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Dec 11 17:28:02 GMT 2021 - 14.6K bytes - Click Count (0) -
helm-releases/minio-3.4.7.tgz
fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Jan 25 20:49:24 GMT 2022 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.1.2.tgz
fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Sep 18 04:26:47 GMT 2021 - 14.4K bytes - Click Count (0) -
helm-releases/minio-3.1.4.tgz
fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Mon Sep 20 05:30:22 GMT 2021 - 14.4K bytes - Click Count (0) -
helm-releases/minio-3.1.5.tgz
fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Sep 22 16:52:01 GMT 2021 - 14.4K bytes - Click Count (0) -
cmd/xl-storage-format-v2.go
// using a delete-marker and MetaSys entries. It's used to track tiered content of a // deleted/overwritten version. This version is visible _only_to the scanner routine, for subsequent deletion. // This kind of tracking is necessary since a version's tiered content is deleted asynchronously. // Backend directory tree structure: // disk1/ // └── bucket // └── object // ├── a192c1d5-9bd5-41fd-9a90-ab10e165398d
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Aug 29 02:39:48 GMT 2025 - 65.6K bytes - Click Count (1)