Search Options

Results per page
Sort
Preferred Languages
Advance

Results 201 - 210 of 250 for comandos (0.04 sec)

  1. 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 ...`
      
    Registered: Fri Dec 26 09:05:12 UTC 2025
    - Last Modified: Fri Sep 05 03:47:18 UTC 2025
    - 456.9K bytes
    - Viewed (1)
  2. CHANGELOG/CHANGELOG-1.11.md

    ### SIG Cluster Lifecycle
    
    Registered: Fri Dec 26 09:05:12 UTC 2025
    - Last Modified: Thu Feb 06 06:04:15 UTC 2020
    - 328.4K bytes
    - Viewed (0)
  3. helm-releases/minio-3.3.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sat Dec 11 17:26:01 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  4. helm-releases/minio-3.3.4.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: Sat Dec 11 17:59:34 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  5. helm-releases/minio-3.4.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Dec 21 02:58:25 UTC 2021
    - 15.2K bytes
    - Viewed (0)
  6. helm-releases/minio-3.4.4.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 Dec 31 04:21:24 UTC 2021
    - 15.2K bytes
    - Viewed (0)
  7. helm-releases/minio-3.4.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: Wed Jan 05 19:32:55 UTC 2022
    - 15.2K bytes
    - Viewed (0)
  8. helm-releases/minio-3.5.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Feb 13 23:43:44 UTC 2022
    - 15.4K bytes
    - Viewed (0)
  9. helm-releases/minio-3.1.9.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 Oct 10 21:28:04 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  10. helm-releases/minio-3.3.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: Thu Nov 25 17:33:26 UTC 2021
    - 14.6K bytes
    - Viewed (0)
Back to top