- Sort Score
- Result 10 results
- Languages All
Results 281 - 290 of 327 for netdfs (0.04 sec)
-
helm-releases/minio-1.0.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 Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 20 22:30:54 UTC 2021 - 13.5K bytes - Viewed (0) -
helm-releases/minio-1.0.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 Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 20 22:32:29 UTC 2021 - 13.5K bytes - Viewed (0) -
helm-releases/minio-1.0.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 Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 24 19:04:07 UTC 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-1.0.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...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Wed Aug 25 02:12:51 UTC 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-1.0.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...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Wed Aug 25 19:53:57 UTC 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-2.0.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 Sep 07 19:28:11 UTC 2025 - Last Modified: Thu Aug 26 07:36:46 UTC 2021 - 13.6K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.20.md
- github.com/stretchr/testify: [v1.4.0 → v1.6.1](https://github.com/stretchr/testify/compare/v1.4.0...v1.6.1) - github.com/vishvananda/netns: [52d707b → db3c7e5](https://github.com/vishvananda/netns/compare/52d707b...db3c7e5) - go.etcd.io/etcd: 17cef6e → dd1b699 - go.opencensus.io: v0.22.2 → v0.22.3 - golang.org/x/crypto: 75b2880 → 7f63de1 - golang.org/x/exp: da58074 → 6cc2880
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Jan 19 21:05:45 UTC 2022 - 409K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.29.md
- `kubeadm`: a separate...
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Mar 12 00:36:01 UTC 2025 - 429.6K bytes - Viewed (1) -
cmd/test-utils_test.go
// initializes a test server with the given object layer and disks. func initTestServerWithBackend(ctx context.Context, t TestErrHandler, testServer TestServer, objLayer ObjectLayer, disks []string) TestServer { // Test Server needs to start before formatting of disks. // Get credential. credentials := globalActiveCred if !globalReplicationPool.IsSet() { globalReplicationPool.Set(nil) } testServer.Obj = objLayer
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 29 02:39:48 UTC 2025 - 77K bytes - Viewed (0) -
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 Sep 05 11:42:10 UTC 2025 - Last Modified: Sun Feb 06 14:55:54 UTC 2022 - 50.8K bytes - Viewed (0)