- Sort Score
- Result 10 results
- Languages All
Results 31 - 40 of 1,118 for Release (0.19 sec)
-
CHANGELOG/CHANGELOG-1.3.md
[kubernetes-client-linux-arm64.tar.gz](https://storage.googleapis.com/kubernetes-release/release/v1.3.10/kubernetes-client-linux-arm64.tar.gz) | `176b52d35150ca9f08a7e90e33e2839b7574afe350edf4fafa46745d77bb5aa4`
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu Dec 24 02:28:26 UTC 2020 - 84K bytes - Viewed (0) -
SECURITY.md
# Security Policy ## Supported Versions We support the past two Go releases (for example, Go 1.17.x and Go 1.18.x when Go 1.18.x is the latest stable release). See https://go.dev/wiki/Go-Release-Cycle and in particular the [Release Maintenance](https://go.dev/wiki/Go-Release-Cycle#release-maintenance) part of that page. ## Reporting a Vulnerability
Registered: Tue Nov 05 11:13:11 UTC 2024 - Last Modified: Fri Sep 22 21:17:24 UTC 2023 - 426 bytes - Viewed (0) -
helm-releases/minio-5.0.8.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Apr 13 21:49:51 UTC 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-5.0.9.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Wed May 03 06:23:26 UTC 2023 - 20.2K bytes - Viewed (0) -
helm-releases/minio-5.0.10.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Sat May 27 00:05:49 UTC 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-3.4.7.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:...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Jan 25 20:49:24 UTC 2022 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.2.0.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:...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Oct 13 02:16:24 UTC 2021 - 14.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:...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Dec 11 17:28:02 UTC 2021 - 14.6K 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 ```
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Jan 24 07:27:57 UTC 2024 - 10.9K bytes - Viewed (0) -
docker-buildx.sh
--build-arg RELEASE="${release}" \ -t "minio/minio:${release}-cpuv1" \ -t "quay.io/minio/minio:${release}-cpuv1" \ --platform=linux/arm64,linux/amd64,linux/ppc64le \ -f Dockerfile.release.old_cpu . docker buildx prune -f docker buildx build --push --no-cache \ --build-arg RELEASE="${release}" \ -t "minio/minio:${release}.fips" \ -t "quay.io/minio/minio:${release}.fips" \ --platform=linux/amd64 -f Dockerfile.release.fips .
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Oct 13 14:06:17 UTC 2024 - 1.2K bytes - Viewed (0)