Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 621 - 630 of 680 for reeds (0.05 seconds)

  1. helm-releases/minio-4.1.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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Mon Oct 24 20:37:05 GMT 2022
    - 20K bytes
    - Click Count (0)
  2. helm-releases/minio-5.1.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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Mar 03 18:49:37 GMT 2024
    - 21.3K bytes
    - Click Count (0)
  3. helm-releases/minio-5.2.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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Apr 28 10:14:37 GMT 2024
    - 21.7K bytes
    - Click Count (0)
  4. CHANGELOG/CHANGELOG-1.17.md

    #### Storage
    - A node that uses a CSI raw block volume needs to be drained before kubelet can be upgraded to 1.17. ([#74026](https://github.com/kubernetes/kubernetes/pull/74026), [@mkimuram](https://github.com/mkimuram))
    
    #### Windows
    Created: Fri Apr 03 09:05:14 GMT 2026
    - Last Modified: Thu Jan 28 10:44:33 GMT 2021
    - 346.2K bytes
    - Click Count (1)
  5. helm-releases/minio-3.5.4.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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Mon Feb 14 06:04:53 GMT 2022
    - 17.2K bytes
    - Click Count (0)
  6. helm-releases/minio-3.5.5.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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Wed Feb 16 19:44:53 GMT 2022
    - 17.2K bytes
    - Click Count (0)
  7. helm-releases/minio-3.5.7.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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Feb 20 08:55:08 GMT 2022
    - 17.6K bytes
    - Click Count (0)
  8. helm-releases/minio-3.5.8.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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Feb 27 06:44:38 GMT 2022
    - 17.7K bytes
    - Click Count (0)
  9. helm-releases/minio-3.6.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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Mar 15 00:13:17 GMT 2022
    - 17.9K bytes
    - Click Count (0)
  10. tensorflow/c/eager/c_api_test.cc

      EXPECT_EQ(tensorflow::DT_INT64, attr_values.find("dtype")->second.type());
    
      TF_DeleteStatus(status);
      TFE_DeleteOp(var_op);
      TFE_DeleteOp(var_op_2);
      TFE_DeleteContext(ctx);
    }
    
    // Needs to work with a const TFE_Op since custom devices should not modify the
    // op they are called with.
    TFE_Op* CloneOp(const TFE_Op* other) {
      TF_Status* status = TF_NewStatus();
    Created: Tue Apr 07 12:39:13 GMT 2026
    - Last Modified: Thu Oct 09 05:56:18 GMT 2025
    - 94.6K bytes
    - Click Count (0)
Back to Top