- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 13 for Bold (0.12 sec)
-
Dockerfile.release.old_cpu
Harshavardhana <******@****.***> 1711791711 -0700
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Mar 30 09:41:56 GMT 2024 - 2.8K bytes - Viewed (0) -
docs/bucket/retention/README.md
### Set legal hold on an object PutObject API allows setting legal hold using `x-amz-object-lock-legal-hold` header. ```sh aws s3api put-object --bucket testbucket --key legalhold --object-lock-legal-hold-status ON --body /etc/issue ```
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/tls/kubernetes/README.md
## 2. Create Kubernetes secret [Kubernetes secrets](https://kubernetes.io/docs/concepts/configuration/secret) are intended to hold sensitive information. We'll use secrets to hold the TLS certificate and key. To create a secret, update the paths to `private.key` and `public.crt` below. Then type ```sh
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 3K bytes - Viewed (0) -
helm/minio/README.md
```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ```
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) -
Makefile
verify-healing-with-rewrite: ## verify healing to rewrite old xl.meta -> new xl.meta @echo "Verify healing with rewrite" @GORACE=history_size=7 CGO_ENABLED=1 go build -race -tags kqueue -trimpath --ldflags "$(LDFLAGS)" -o $(PWD)/minio 1>/dev/null @(env bash $(PWD)/buildscripts/rewrite-old-new.sh) verify-healing-inconsistent-versions: ## verify resolving inconsistent versions
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 25 21:55:41 GMT 2024 - 10.3K bytes - Viewed (1) -
docs/site-replication/README.md
- Creation and deletion of service accounts (except those owned by the root user) - Changes to Bucket features such as: - Bucket Policies - Bucket Tags - Bucket Object-Lock configurations (including retention and legal hold configuration) - Bucket Encryption configuration > NOTE: Bucket versioning is automatically enabled for all new and existing buckets on all replicated sites.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Feb 26 21:30:28 GMT 2024 - 3.4K bytes - Viewed (0) -
docs/bucket/lifecycle/README.md
## 2. Enable bucket lifecycle configuration - Create a bucket lifecycle configuration which expires the objects under the prefix `old/` on `2020-01-01T00:00:00.000Z` date and the objects under `temp/` after 7 days. - Enable bucket lifecycle configuration using `mc`: ```sh $ mc ilm import play/testbucket <<EOF { "Rules": [ {
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Aug 26 07:33:25 GMT 2023 - 9K bytes - Viewed (1) -
docs/bucket/lifecycle/DESIGN.md
### Expiry or removal events An object that is in transition tier will be deleted once the object hits expiry date or if removed via `mc rm` (`mc rm --vid` in the case of delete of a specific object version). Other rules specific to legal hold and object locking precede any lifecycle rules. ### Additional notes Tiering and lifecycle transition are applicable only to erasure/distributed MinIO. ## Explore Further
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 4.3K bytes - Viewed (0) -
LICENSE
A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 23 18:58:53 GMT 2021 - 33.7K bytes - Viewed (0) -
docs/distributed/DECOMMISSION.md
# Decommissioning Decommissiong is a mechanism in MinIO to drain older pools (usually with old hardware) and migrate the content from such pools to a newer pools (usually better hardware). Decommissioning spreads the data across all pools - for example, if you decommission `pool1`, all the data from `pool1` spreads across `pool2` and `pool3`. ## Features
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Jul 11 14:59:49 GMT 2022 - 8.3K bytes - Viewed (0)