Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 211 - 220 of 304 for Upgraded (0.07 seconds)

  1. helm-releases/minio-4.0.0.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: Tue Apr 26 02:41:39 GMT 2022
    - 18K bytes
    - Click Count (0)
  2. helm-releases/minio-5.0.1.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 Nov 13 10:04:51 GMT 2022
    - 19.8K bytes
    - Click Count (0)
  3. helm-releases/minio-4.0.6.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 Jul 24 03:34:14 GMT 2022
    - 18.4K bytes
    - Click Count (0)
  4. docs/SMB3_IMPLEMENTATION_PLAN.md

    - [ ] Implement lease key generation and management
    - [ ] Add lease context to Create request/response
    - [ ] Implement lease break notification handling
    - [ ] Modify SmbFile to support lease-based caching
    - [ ] Add lease upgrade/downgrade logic
    - [ ] Implement lease epoch tracking for v2 leases
    
    #### 1.3 Integration Points
    - Modify `Smb2CreateRequest` to include lease contexts
    - Update `SmbFile` caching logic to use leases
    Created: Sat Dec 20 13:44:44 GMT 2025
    - Last Modified: Sat Aug 16 02:53:50 GMT 2025
    - 10.7K bytes
    - Click Count (0)
  5. helm-releases/minio-1.0.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 Aug 24 18:58:05 GMT 2021
    - 13.6K bytes
    - Click Count (0)
  6. helm-releases/minio-3.6.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 can...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Wed Apr 13 22:45:54 GMT 2022
    - 18K bytes
    - Click Count (0)
  7. helm-releases/minio-4.0.1.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: Mon May 02 06:10:34 GMT 2022
    - 18K bytes
    - Click Count (0)
  8. helm-releases/minio-4.0.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 can...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Thu Jul 14 04:44:23 GMT 2022
    - 18.2K bytes
    - Click Count (0)
  9. helm-releases/minio-4.0.9.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: Wed Aug 03 06:10:44 GMT 2022
    - 18.6K bytes
    - Click Count (0)
  10. okhttp/src/commonJvmAndroid/kotlin/okhttp3/ConnectionSpec.kt

            .build()
    
        /**
         * A backwards-compatible fallback configuration that works on obsolete client platforms and can
         * connect to obsolete servers. When possible, prefer to upgrade your client platform or server
         * rather than using this configuration.
         */
        @JvmField
        val COMPATIBLE_TLS =
          Builder(true)
            .cipherSuites(*APPROVED_CIPHER_SUITES.toTypedArray())
    Created: Fri Dec 26 11:42:13 GMT 2025
    - Last Modified: Fri Dec 27 13:39:56 GMT 2024
    - 13.4K bytes
    - Click Count (0)
Back to Top