- Sort Score
- Result 10 results
- Languages All
Results 31 - 40 of 365 for released (0.05 sec)
-
helm-releases/minio-1.0.0.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/...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
.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/...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
.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/...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
.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/...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
.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/...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
.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/...Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Thu Aug 26 07:36:46 UTC 2021 - 13.6K bytes - Viewed (0) -
cmd/object-api-utils.go
compressOpts = append(compressOpts, s2.WriterBetterCompression()) } } // newS2CompressReader will read data from r, compress it and return the compressed data as a Reader. // Use Close to ensure resources are released on incomplete streams. // // input 'on' is always recommended such that this function works // properly, because we do not wish to create an object even if // client closed the stream prematurely.
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Wed Jun 25 15:08:54 UTC 2025 - 37.3K bytes - Viewed (0) -
.github/workflows/close-linked-issue-when-merged-into-release.yml
name: Close linked issues when PR merged into release on: pull_request: types: [closed] branches: - release - release7x - release8x permissions: issues: write jobs: closeIssueOnPrMerge: runs-on: ubuntu-latest steps: - name: Closes issues related to a merged pull request. uses: ldez/gha-mjolnir@df0e84242364946fa3ad4e7556510e8086ad681a env:Registered: Wed Sep 10 11:36:15 UTC 2025 - Last Modified: Wed Jul 16 09:18:51 UTC 2025 - 458 bytes - Viewed (0) -
.teamcity/src/main/kotlin/common/VersionedSettingsBranch.kt
) { /** * 0~23. * To avoid nightly promotion jobs running at the same time, * we run each branch on different hours. * master - 0:00 * release - 1:00 * release6x - 2:00 * release7x - 3:00 * ... * releaseNx - (N-4):00 */ val nightlyPromotionTriggerHour: Int? = determineNightlyPromotionTriggerHour(branchName) /**Registered: Wed Sep 10 11:36:15 UTC 2025 - Last Modified: Tue Jun 17 09:57:45 UTC 2025 - 3.8K bytes - Viewed (0) -
Dockerfile.release.old_cpu
curl -s -q https://dl.min.io/server/minio/release/linux-${TARGETARCH}/archive/minio.${RELEASE}.sha256sum -o /go/bin/minio.sha256sum && \ chmod +x /go/bin/minio # Download mc binary and signature files RUN curl -s -q https://dl.min.io/client/mc/release/linux-${TARGETARCH}/mc -o /go/bin/mc && \Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Wed Apr 09 14:28:39 UTC 2025 - 3.1K bytes - Viewed (0)