- Sort Score
- Num 10 results
- Language All
Results 241 - 250 of 289 for comandos (0.06 seconds)
-
helm-releases/minio-3.0.1.tgz
"NodePort" }} Minio can be accessed via port {{ .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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Thu Sep 02 01:47:43 GMT 2021 - 13.8K bytes - Click Count (0) -
helm-releases/minio-3.0.2.tgz
"NodePort" }} Minio can be accessed via port {{ .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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Fri Sep 03 08:11:32 GMT 2021 - 13.8K bytes - Click Count (0) -
helm-releases/minio-3.1.0.tgz
"NodePort" }} Minio can be accessed via port {{ .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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Sun Sep 12 18:19:27 GMT 2021 - 14.3K bytes - Click Count (0) -
helm-releases/minio-3.1.1.tgz
"NodePort" }} Minio can be accessed via port {{ .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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Mon Sep 13 16:43:10 GMT 2021 - 14.3K bytes - Click Count (0) -
helm-releases/minio-3.1.6.tgz
"NodePort" }} Minio can be accessed via port {{ .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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Thu Sep 23 19:56:39 GMT 2021 - 14.5K bytes - Click Count (0) -
helm-releases/minio-3.4.7.tgz
"NodePort" }} MinIO can be accessed via port {{ .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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Tue Jan 25 20:49:24 GMT 2022 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.3.3.tgz
"NodePort" }} MinIO can be accessed via port {{ .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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Sat Dec 11 17:28:02 GMT 2021 - 14.6K bytes - Click Count (0) -
helm-releases/minio-3.2.0.tgz
"NodePort" }} Minio can be accessed via port {{ .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...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Wed Oct 13 02:16:24 GMT 2021 - 14.6K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.28.md
- The helping message of commands which have sub-commands is now clearer and more instructive. It will show the full command instead of `kubectl <command> --help ...`
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Fri Sep 05 03:47:18 GMT 2025 - 456.9K bytes - Click Count (1) -
CHANGELOG/CHANGELOG-1.36.md
- Kubeadm: bumped the timeout of the `kubeadm upgrade` `CreateJob` preflight check to 1 minute. This allows...
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Mar 19 23:38:00 GMT 2026 - 142.1K bytes - Click Count (0)