- Sort Score
- Num 10 results
- Language All
Results 281 - 290 of 375 for Generics (0.07 seconds)
-
helm-releases/minio-4.0.12.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: ```...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Aug 14 05:50:43 GMT 2022 - 19.4K bytes - Click Count (0) -
helm-releases/minio-5.4.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: ```...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Jan 03 05:34:47 GMT 2025 - 21.7K bytes - Click Count (0) -
helm-releases/minio-3.5.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: ```...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Feb 02 00:16:41 GMT 2022 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.5.1.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: ```...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Feb 04 22:54:20 GMT 2022 - 15.4K bytes - Click Count (0) -
helm-releases/minio-3.1.7.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: ```...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Oct 03 22:23:22 GMT 2021 - 14.6K bytes - Click Count (0) -
helm-releases/minio-3.3.1.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: ```...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Dec 02 20:09:18 GMT 2021 - 14.6K bytes - Click Count (0) -
helm-releases/minio-3.5.6.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: ```...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Feb 19 20:34:14 GMT 2022 - 17.6K bytes - Click Count (0) -
helm-releases/minio-3.5.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: ```...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Mar 03 23:29:03 GMT 2022 - 17.7K bytes - Click Count (0) -
helm-releases/minio-3.6.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: ```...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Mar 24 04:07:15 GMT 2022 - 17.9K bytes - Click Count (0) -
internal/s3select/unused-errors.go
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Feb 20 08:16:35 GMT 2024 - 17.5K bytes - Click Count (0)