Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 201 - 210 of 291 for comandos (0.05 seconds)

  1. helm-releases/minio-5.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: Sun Apr 28 10:14:37 GMT 2024
    - 21.7K bytes
    - Click Count (0)
  2. 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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Apr 17 21:46:44 GMT 2022
    - 18.2K bytes
    - Click Count (0)
  3. 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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Apr 26 02:41:39 GMT 2022
    - 18K bytes
    - Click Count (0)
  4. 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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Nov 13 10:04:51 GMT 2022
    - 19.8K bytes
    - Click Count (0)
  5. 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...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Jul 24 03:34:14 GMT 2022
    - 18.4K bytes
    - Click Count (0)
  6. CHANGELOG/CHANGELOG-1.12.md

    * Fixes ability for admin/edit/view users to see controller revisions, needed for kubectl rollout commands ([#70699](https://github.com/kubernetes/kubernetes/pull/70699), [@liggitt](https://github.com/liggitt))
    Created: Fri Apr 03 09:05:14 GMT 2026
    - Last Modified: Thu Feb 06 06:04:15 GMT 2020
    - 293.8K bytes
    - Click Count (0)
  7. 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`...
    Created: Fri Apr 03 09:05:14 GMT 2026
    - Last Modified: Tue Feb 28 21:06:52 GMT 2023
    - 424.5K bytes
    - Click Count (0)
  8. helm-releases/minio-3.5.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: Sun Feb 20 08:55:08 GMT 2022
    - 17.6K bytes
    - Click Count (0)
  9. helm-releases/minio-3.5.8.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 Feb 27 06:44:38 GMT 2022
    - 17.7K bytes
    - Click Count (0)
  10. helm-releases/minio-3.6.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: Tue Mar 15 00:13:17 GMT 2022
    - 17.9K bytes
    - Click Count (0)
Back to Top