- Sort Score
- Result 10 results
- Languages All
Results 331 - 340 of 497 for centric (0.1 sec)
-
helm-releases/minio-3.4.4.tgz
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 minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or the `--set` parameter: ```...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Dec 31 04:21:24 UTC 2021 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.4.5.tgz
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 minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or the `--set` parameter: ```...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Jan 05 19:32:55 UTC 2022 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.5.3.tgz
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 minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or the `--set` parameter: ```...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Feb 13 23:43:44 UTC 2022 - 15.4K bytes - Viewed (0) -
helm-releases/minio-3.3.2.tgz
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 minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or the `--set` parameter: ```...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Dec 11 17:26:01 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.3.4.tgz
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 minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or the `--set` parameter: ```...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Dec 11 17:59:34 UTC 2021 - 14.6K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.19.md
- It...
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Jan 05 05:42:32 UTC 2022 - 489.7K bytes - Viewed (0) -
helm-releases/minio-4.0.15.tgz
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 minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or the `--set` parameter: ```...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Sep 21 11:07:01 UTC 2022 - 20K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.20.md
- Add a metric for time taken to perform recursive permission change ([#95866](https://github.com/kubernetes/kubernetes/pull/95866), [@JornShen](https://github.com/JornShen)) [SIG Instrumentation and Storage]
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Jan 19 21:05:45 UTC 2022 - 409K bytes - Viewed (0) -
helm-releases/minio-3.1.9.tgz
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 minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or the `--set` parameter: ```...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Oct 10 21:28:04 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.3.0.tgz
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 minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or the `--set` parameter: ```...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Nov 25 17:33:26 UTC 2021 - 14.6K bytes - Viewed (0)