- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 15 for liven (0.12 sec)
-
docs/bucket/lifecycle/README.md
### 3.1 Automatic removal of non current objects versions A non-current object version is a version which is not the latest for a given object. It is possible to set up an automatic removal of non-current versions when a version becomes older than a given number of days. e.g., To scan objects stored under `user-uploads/` prefix and remove versions older than one year. ``` { "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/orchestration/README.md
> In a cloud-native environment, scalability is not a function of the application but the orchestration platform. In a typical modern infrastructure deployment, application, database, key-store, etc. already live in containers and are managed by orchestration platforms. MinIO brings robust, scalable, AWS S3 compatible object storage to the lot.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 2.2K bytes - Viewed (0) -
docs/multi-user/README.md
- `jwt:sub` - `jwt:iss` - `jwt:aud` - `jwt:jti` - `jwt:upn` - `jwt:name` - `jwt:groups` - `jwt:given_name` - `jwt:family_name` - `jwt:middle_name` - `jwt:nickname` - `jwt:preferred_username` - `jwt:profile` - `jwt:picture` - `jwt:website` - `jwt:email` - `jwt:gender` - `jwt:birthdate`
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Mar 21 06:38:06 GMT 2023 - 8K bytes - Viewed (0) -
docs/bucket/retention/README.md
- In `Compliance` mode, objects cannot be deleted by anyone until retention period has expired for the given version id. If user has governance bypass permissions, an object's retention date can be extended in `Compliance` mode. - Once object lock configuration is set to a bucket
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) -
manifests/charts/gateway/README.md
For consistency, the same profiles are used across each chart, even if they do not impact a given chart. Explicitly set values have highest priority, then profile settings, then chart defaults. As an implementation detail of profiles, the default values for the chart are all nested under `defaults`.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 19:38:07 GMT 2024 - 6.6K bytes - Viewed (0) -
docs/kms/README.md
└────────────┘ │ KMS │ └─────────┘ ``` In a given setup, there are `n` MinIO instances talking to `m` KES servers but only `1` central KMS. The most simple setup consists of `1` MinIO server or cluster talking to `1` KMS via `1` KES server.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 7.1K bytes - Viewed (0) -
manifests/charts/ztunnel/README.md
For consistency, the same profiles are used across each chart, even if they do not impact a given chart. Explicitly set values have highest priority, then profile settings, then chart defaults. As an implementation detail of profiles, the default values for the chart are all nested under `defaults`.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 1.3K bytes - Viewed (0) -
docs/metrics/README.md
MinIO server has two healthcheck related un-authenticated endpoints, a liveness probe to indicate if server is responding, cluster probe to check if server can be taken down for maintenance. - Liveness probe available at `/minio/health/live` - Cluster probe available at `/minio/health/cluster` Read more on how to use these endpoints in [MinIO healthcheck guide](https://github.com/minio/minio/blob/master/docs/metrics/healthcheck/README.md). ## Prometheus Probe
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Feb 29 18:35:20 GMT 2024 - 1.9K bytes - Viewed (0) -
docs/metrics/healthcheck/README.md
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jul 06 16:18:38 GMT 2023 - 2.5K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/README.md
For consistency, the same profiles are used across each chart, even if they do not impact a given chart. Explicitly set values have highest priority, then profile settings, then chart defaults. As an implementation detail of profiles, the default values for the chart are all nested under `defaults`.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 2K bytes - Viewed (0)