- Sort Score
- Num 10 results
- Language All
Results 311 - 320 of 374 for upgraded (0.06 seconds)
-
helm-releases/minio-3.3.2.tgz
values using the command: ```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 ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Dec 11 17:26:01 GMT 2021 - 14.6K bytes - Click Count (0) -
helm-releases/minio-3.3.4.tgz
values using the command: ```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 ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Dec 11 17:59:34 GMT 2021 - 14.6K bytes - Click Count (0) -
helm-releases/minio-3.4.2.tgz
values using the command: ```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 ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Dec 21 02:58:25 GMT 2021 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.4.4.tgz
values using the command: ```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 ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Dec 31 04:21:24 GMT 2021 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.4.5.tgz
values using the command: ```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 ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Jan 05 19:32:55 GMT 2022 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.5.3.tgz
values using the command: ```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 ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Feb 13 23:43:44 GMT 2022 - 15.4K bytes - Click Count (0) -
cmd/data-scanner_test.go
// Prepare lifecycle expiration workers es := newExpiryState(t.Context(), objAPI, 0) globalExpiryState = es // Prepare object versions obj := "obj-1" // Simulate objects uploaded 30 hours ago modTime := now.Add(-48 * time.Hour) uuids := make([]uuid.UUID, 5) for i := range uuids { uuids[i] = uuid.UUID([16]byte{15: uint8(i + 1)}) } fivs := make([]FileInfo, 5)
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Aug 29 02:39:48 GMT 2025 - 12K bytes - Click Count (0) -
mockwebserver/src/main/kotlin/mockwebserver3/MockWebServer.kt
return false } var reuseSocket = true val requestWantsSocket = "Upgrade".equals(request.headers["Connection"], ignoreCase = true) val requestWantsWebSocket = requestWantsSocket && "websocket".equals(request.headers["Upgrade"], ignoreCase = true) val responseWantsSocket = response.socketHandler != nullCreated: Fri Dec 26 11:42:13 GMT 2025 - Last Modified: Sat Aug 02 20:36:00 GMT 2025 - 40.3K bytes - Click Count (0) -
docs/en/docs/tutorial/query-params-str-validations.md
/// info FastAPI added support for `Annotated` (and started recommending it) in version 0.95.0. If you have an older version, you would get errors when trying to use `Annotated`. Make sure you [Upgrade the FastAPI version](../deployment/versions.md#upgrading-the-fastapi-versions){.internal-link target=_blank} to at least 0.95.1 before using `Annotated`. ///
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Dec 20 15:55:38 GMT 2025 - 16.7K bytes - Click Count (0) -
cmd/global-heal.go
} send(result) return } var versionNotFound int for _, version := range fivs.Versions { // Ignore healing a version if: // - It is uploaded after the drive healing is started // - An object that is already expired by ILM rule. if !started.IsZero() && version.ModTime.After(started) || filterLifecycle(bucket, version.Name, version) { versionNotFound++
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Apr 04 13:49:12 GMT 2025 - 16.2K bytes - Click Count (0)