Search Options

Results per page
Sort
Preferred Languages
Advance

Results 301 - 310 of 386 for feeds (0.04 sec)

  1. docs/changelogs/changelog_3x.md

        memory!
    
        The best practice in OkHttp 3 is to create a single OkHttpClient instance
        and share it throughout the application. Requests that needs a customized
        client should call `OkHttpClient.newBuilder()` on that shared instance.
        This allows customization without the drawbacks of separate connection
        pools.
    
    Registered: Fri Nov 01 11:42:11 UTC 2024
    - Last Modified: Sun Feb 06 14:55:54 UTC 2022
    - 50.8K bytes
    - Viewed (0)
  2. helm-releases/minio-3.1.9.tgz

    Kubernetes secret and providing it to Helm via the `trustedCertsSecret` value. If `.Values.tls.enabled` is `true` and you're installing certificates for third party CAs, remember to include Minio's own certificate with key `public.crt`, if it also needs to be trusted. For instance, given that TLS is enabled and you need to add trust for Minio's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Oct 10 21:28:04 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  3. helm-releases/minio-3.3.0.tgz

    Kubernetes secret and providing it to Helm via the `trustedCertsSecret` value. If `.Values.tls.enabled` is `true` and you're installing certificates for third party CAs, remember to include Minio's own certificate with key `public.crt`, if it also needs to be trusted. For instance, given that TLS is enabled and you need to add trust for Minio's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Nov 25 17:33:26 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  4. helm-releases/minio-3.4.0.tgz

    Kubernetes secret and providing it to Helm via the `trustedCertsSecret` value. If `.Values.tls.enabled` is `true` and you're installing certificates for third party CAs, remember to include MinIO's own certificate with key `public.crt`, if it also needs to be trusted. For instance, given that TLS is enabled and you need to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Dec 19 22:32:49 UTC 2021
    - 14.8K bytes
    - Viewed (0)
  5. helm-releases/minio-3.4.1.tgz

    Kubernetes secret and providing it to Helm via the `trustedCertsSecret` value. If `.Values.tls.enabled` is `true` and you're installing certificates for third party CAs, remember to include MinIO's own certificate with key `public.crt`, if it also needs to be trusted. For instance, given that TLS is enabled and you need to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Mon Dec 20 21:11:50 UTC 2021
    - 15.2K bytes
    - Viewed (0)
  6. helm-releases/minio-3.5.6.tgz

    Kubernetes secret and providing it to Helm via the `trustedCertsSecret` value. If `.Values.tls.enabled` is `true` and you're installing certificates for third party CAs, remember to include MinIO's own certificate with key `public.crt`, if it also needs to be trusted. For instance, given that TLS is enabled and you need to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sat Feb 19 20:34:14 UTC 2022
    - 17.6K bytes
    - Viewed (0)
  7. helm-releases/minio-3.5.9.tgz

    Kubernetes secret and providing it to Helm via the `trustedCertsSecret` value. If `.Values.tls.enabled` is `true` and you're installing certificates for third party CAs, remember to include MinIO's own certificate with key `public.crt`, if it also needs to be trusted. For instance, given that TLS is enabled and you need to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Mar 03 23:29:03 UTC 2022
    - 17.7K bytes
    - Viewed (0)
  8. helm-releases/minio-3.6.3.tgz

    Kubernetes secret and providing it to Helm via the `trustedCertsSecret` value. If `.Values.tls.enabled` is `true` and you're installing certificates for third party CAs, remember to include MinIO's own certificate with key `public.crt`, if it also needs to be trusted. For instance, given that TLS is enabled and you need to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Mar 24 04:07:15 UTC 2022
    - 17.9K bytes
    - Viewed (0)
  9. helm-releases/minio-4.0.15.tgz

    Kubernetes secret and providing it to Helm via the `trustedCertsSecret` value. If `.Values.tls.enabled` is `true` and you're installing certificates for third party CAs, remember to include MinIO's own certificate with key `public.crt`, if it also needs to be trusted. For instance, given that TLS is enabled and you need to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Wed Sep 21 11:07:01 UTC 2022
    - 20K bytes
    - Viewed (0)
  10. guava/src/com/google/common/cache/LocalCache.java

         * purposes, the "count" field, tracking the number of elements, serves as that volatile
         * variable ensuring visibility. This is convenient because this field needs to be read in many
         * read operations anyway:
         *
         * - All (unsynchronized) read operations must first read the "count" field, and should not look
         * at table entries if it is 0.
         *
    Registered: Fri Nov 01 12:43:10 UTC 2024
    - Last Modified: Fri Oct 18 19:07:49 UTC 2024
    - 149.2K bytes
    - Viewed (0)
Back to top