Search Options

Results per page
Sort
Preferred Languages
Advance

Results 151 - 160 of 250 for comandos (0.05 sec)

  1. helm-releases/minio-5.0.5.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Feb 03 20:54:02 UTC 2023
    - 20.3K bytes
    - Viewed (0)
  2. helm-releases/minio-4.0.14.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Mon Sep 05 01:06:49 UTC 2022
    - 19.6K bytes
    - Viewed (0)
  3. helm-releases/minio-4.0.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Thu Jul 28 03:54:38 UTC 2022
    - 18.6K bytes
    - Viewed (0)
  4. helm-releases/minio-4.0.10.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Thu Aug 04 16:09:22 UTC 2022
    - 19.2K bytes
    - Viewed (0)
  5. helm-releases/minio-3.6.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Apr 17 21:46:44 UTC 2022
    - 18.2K bytes
    - Viewed (0)
  6. helm-releases/minio-4.0.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Apr 26 02:41:39 UTC 2022
    - 18K bytes
    - Viewed (0)
  7. helm-releases/minio-5.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Nov 13 10:04:51 UTC 2022
    - 19.8K bytes
    - Viewed (0)
  8. helm-releases/minio-4.0.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Jul 24 03:34:14 UTC 2022
    - 18.4K bytes
    - Viewed (0)
  9. helm-releases/minio-2.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Aug 31 09:09:09 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  10. CHANGELOG/CHANGELOG-1.23.md

    - `--log-flush-frequency` had no effect in several commands or was missing. Help and warning texts were not always using the right format for a command (`add_dir_header` instead of `add-dir-header`). Fixing this included cleaning up flag handling in component-base/logs: that package no longer adds flags to the global flag sets. Commands which want the klog and `--log-flush-frequency` flags must explicitly call `logs.AddFlags`; the new `cli.Run`...
    Registered: Fri Dec 26 09:05:12 UTC 2025
    - Last Modified: Tue Feb 28 21:06:52 UTC 2023
    - 424.5K bytes
    - Viewed (0)
Back to top