- Sort Score
- Num 10 results
- Language All
Results 211 - 220 of 1,070 for released (0.12 seconds)
-
helm-releases/minio-5.0.11.tgz
.Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Wed Jun 21 19:29:09 GMT 2023 - 20.3K bytes - Click Count (0) -
helm-releases/minio-5.0.12.tgz
.Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Fri Jul 07 16:44:16 GMT 2023 - 20.4K bytes - Click Count (0) -
helm-releases/minio-5.0.13.tgz
.Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Sun Jul 09 07:13:05 GMT 2023 - 20.3K bytes - Click Count (0) -
helm-releases/minio-5.3.0.tgz
}} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.{{ .Values.clusterDomain }} To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kub...Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Fri Oct 11 12:21:05 GMT 2024 - 21.7K bytes - Click Count (0) -
src/main/java/jcifs/smb/SmbFile.java
// Let connection pooling handle cleanup - this improves performance // for scenarios where the same file or directory is accessed multiple times log.trace("Tree handle released to connection pool for reuse"); // The connection pool will handle cleanup based on its own timeout settings } } // Clear attribute cache only if we're doing strict cleanupCreated: Sun Apr 05 00:10:12 GMT 2026 - Last Modified: Sat Aug 30 05:58:03 GMT 2025 - 103.2K bytes - Click Count (0) -
android/guava-tests/test/com/google/common/util/concurrent/FuturesTest.java
* the combiner is almost certain to hold its own reference to the futures, and a real app would * hold a reference to the executor and thus to the combiner. What we really care about is that * the futures are released once the combiner is done running. But we happen to provide this * earlier cleanup at the moment, so we're testing it. */ GcFinalization.awaitClear(future1Ref); GcFinalization.awaitClear(future2Ref);Created: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Mon Mar 16 22:45:21 GMT 2026 - 134K bytes - Click Count (0) -
guava-tests/test/com/google/common/util/concurrent/FuturesTest.java
* the combiner is almost certain to hold its own reference to the futures, and a real app would * hold a reference to the executor and thus to the combiner. What we really care about is that * the futures are released once the combiner is done running. But we happen to provide this * earlier cleanup at the moment, so we're testing it. */ GcFinalization.awaitClear(future1Ref); GcFinalization.awaitClear(future2Ref);Created: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Mon Mar 16 22:45:21 GMT 2026 - 134K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.9.md
Please see the [Releases Page](https://github.com/kubernetes/kubernetes/releases) for older releases. Release notes of older releases can be found in: - [CHANGELOG-1.2.md](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.2.md)
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Tue Nov 16 10:46:27 GMT 2021 - 313.7K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.18.md
### Introducing Windows CSI support alpha for Kubernetes With the release of Kubernetes 1.18, an alpha version of CSI Proxy for Windows is getting released. CSI proxy enables non-privileged (pre-approved) containers to perform privileged storage operations on Windows. CSI drivers can now be supported in Windows by leveraging CSI proxy. SIG Storage made a lot of progress in the 1.18 release.
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Wed Jun 16 17:18:28 GMT 2021 - 373.2K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.6.md
* Federated Ingress Proposal ([#29793](https://github.com/kubernetes/kubernetes/pull/29793), [@quinton-hoole](https://github.com/quinton-hoole)) Please see the [Releases Page](https://github.com/kubernetes/kubernetes/releases) for older releases. Release notes of older releases can be found in: - [CHANGELOG-1.2.md](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.2.md)
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Dec 24 02:28:26 GMT 2020 - 304K bytes - Click Count (0)