- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 123 for releases (1.33 sec)
-
Makefile
@scp -q -r minio-release/$(GOOS)-$(GOARCH)/* ******@****.***:~/releases/server/minio/hotfixes/linux-amd64/archive @scp -q -r minio-release/$(GOOS)-$(GOARCH)/* ******@****.***:~/releases/server/minio/hotfixes/linux-amd64/ @scp -q -r minio-release/$(GOOS)-$(GOARCH)/* ******@****.***:~/releases/server/minio/hotfixes/linux-amd64/archive
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 25 21:55:41 GMT 2024 - 10.3K bytes - Viewed (1) -
cmd/handler-utils.go
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 04 12:04:40 GMT 2024 - 15.5K bytes - Viewed (3) -
cmd/format-erasure.go
continue } // NOTE: This code is specifically needed when migrating version // V1 to V2 to V3, in a scenario such as this we only need to handle // single sets since we never used to support multiple sets in releases // with V1 format version. if len(format.Erasure.Sets) > 1 { continue } if format.Erasure.This == "" { return true } } return false }
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri May 03 15:54:03 GMT 2024 - 23.2K bytes - Viewed (0) -
helm/minio/README.md
You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Jan 24 07:27:57 GMT 2024 - 10.9K 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/...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Aug 26 07:36:46 GMT 2021 - 13.6K 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/...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Aug 24 19:04:07 GMT 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-3.3.3.tgz
apiVersion: {{ template "minio.networkPolicy.apiVersion" . }} metadata: name: {{ template "minio.fullname" . }} namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }} chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} spec: podSelector: matchLabels: app: {{ template "minio.name" . }} release: {{ .Release.Name }} ingress: - ports: - port: {{ .Values.service.port }} {{- if not .Values.networkPolicy.allowExternal }} from: - podSelector:...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Dec 11 17:28:02 GMT 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.4.4.tgz
apiVersion: {{ template "minio.networkPolicy.apiVersion" . }} metadata: name: {{ template "minio.fullname" . }} namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }} chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} spec: podSelector: matchLabels: app: {{ template "minio.name" . }} release: {{ .Release.Name }} ingress: - ports: - port: {{ .Values.service.port }} {{- if not .Values.networkPolicy.allowExternal }} from: - podSelector:...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Dec 31 04:21:24 GMT 2021 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.1.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/...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Sep 20 05:30:22 GMT 2021 - 14.4K bytes - Viewed (0) -
helm-releases/minio-3.5.2.tgz
apiVersion: {{ template "minio.networkPolicy.apiVersion" . }} metadata: name: {{ template "minio.fullname" . }} namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }} chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} spec: podSelector: matchLabels: app: {{ template "minio.name" . }} release: {{ .Release.Name }} ingress: - ports: - port: {{ .Values.service.port }} {{- if not .Values.networkPolicy.allowExternal }} from: - podSelector:...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Feb 08 00:29:26 GMT 2022 - 15.4K bytes - Viewed (0)