Search Options

Results per page
Sort
Preferred Languages
Advance

Results 681 - 690 of 754 for nerede (0.1 sec)

  1. helm-releases/minio-3.6.3.tgz

    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 generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Mar 24 04:07:15 UTC 2022
    - 17.9K bytes
    - Viewed (0)
  2. helm-releases/minio-3.6.2.tgz

    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 generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Mar 17 18:30:55 UTC 2022
    - 17.9K bytes
    - Viewed (0)
  3. helm-releases/minio-3.5.0.tgz

    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 generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Wed Feb 02 00:16:41 UTC 2022
    - 15.2K bytes
    - Viewed (0)
  4. helm-releases/minio-3.5.1.tgz

    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 generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Feb 04 22:54:20 UTC 2022
    - 15.4K bytes
    - Viewed (0)
  5. helm-releases/minio-3.1.7.tgz

    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 generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Oct 03 22:23:22 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  6. helm-releases/minio-3.3.1.tgz

    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 generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Dec 02 20:09:18 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  7. CHANGELOG/CHANGELOG-1.28.md

      with the number of existing entries in the internal cache
      
      - `rest_client_transport_create_calls_total` is a counter
      that increments each time a new transport is created, storing
      the result of the operation needed to generate it: hit, miss
      or uncacheable. ([#117295](https://github.com/kubernetes/kubernetes/pull/117295), [@aojea](https://github.com/aojea))
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Wed Oct 23 04:34:59 UTC 2024
    - 456.9K bytes
    - Viewed (0)
  8. helm-releases/minio-3.6.0.tgz

    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 generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Mar 13 22:44:21 UTC 2022
    - 17.9K bytes
    - Viewed (0)
  9. helm-releases/minio-3.4.3.tgz

    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 generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Tue Dec 21 20:55:50 UTC 2021
    - 17.7K bytes
    - Viewed (0)
  10. CHANGELOG/CHANGELOG-1.9.md

    * Action required: validation rule on metadata.initializers.pending[x].name is tightened. The initializer name needs to contain at least three segments separated by dots. If you create objects with pending initializers, (i.e., not relying on apiserver adding pending initializers according to initializerconfiguration), you need to update the initializer name in existing objects and in configuration files to comply to the new validation rule. ([#51283](https://github....
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Tue Nov 16 10:46:27 UTC 2021
    - 313.7K bytes
    - Viewed (0)
Back to top