Search Options

Results per page
Sort
Preferred Languages
Advance

Results 141 - 150 of 250 for comandos (0.04 sec)

  1. helm-releases/minio-3.6.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: Sun Mar 13 22:44:21 UTC 2022
    - 17.9K bytes
    - Viewed (0)
  2. helm-releases/minio-3.4.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: Tue Dec 21 20:55:50 UTC 2021
    - 17.7K bytes
    - Viewed (0)
  3. helm-releases/minio-5.4.0.tgz

    runAsUser: 1000 runAsGroup: 1000 resources: requests: memory: 128Mi ## Additional volumes to add to the post-job. extraVolumes: [] # - name: extra-policies # configMap: # name: my-extra-policies-cm ## Additional volumeMounts to add to the custom commands container when ## running the post-job. extraVolumeMounts: [] # - name: extra-policies # mountPath: /mnt/extras/ # Command to run after the main command on exit exitCommand: "" ## Merge jobs postJob: podAnnotations: {} annotations: {} securityContext:...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Jan 03 05:34:47 UTC 2025
    - 21.7K bytes
    - Viewed (0)
  4. helm-releases/minio-5.3.0.tgz

    runAsUser: 1000 runAsGroup: 1000 resources: requests: memory: 128Mi ## Additional volumes to add to the post-job. extraVolumes: [] # - name: extra-policies # configMap: # name: my-extra-policies-cm ## Additional volumeMounts to add to the custom commands container when ## running the post-job. extraVolumeMounts: [] # - name: extra-policies # mountPath: /mnt/extras/ # Command to run after the main command on exit exitCommand: "" ## Merge jobs postJob: podAnnotations: {} annotations: {} securityContext:...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Oct 11 12:21:05 UTC 2024
    - 21.7K bytes
    - Viewed (0)
  5. docs/es/docs/async.md

    ---
    
    Imagina que eres la computadora / programa 🤖 en esa historia.
    
    Mientras estás en la fila, estás inactivo 😴, esperando tu turno, sin hacer nada muy "productivo". Pero la fila es rápida porque el cajero solo está tomando los pedidos (no preparándolos), así que está bien.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 10:15:01 UTC 2025
    - 25.4K bytes
    - Viewed (0)
  6. CHANGELOG/CHANGELOG-1.21.md

    ### Default Container Annotation
    
    Pod with multiple containers can use `kubectl.kubernetes.io/default-container` annotation to have a container preselected for kubectl commands. More can be read in [KEP-2227](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cli/2227-kubectl-default-container/README.md).
    
    ### Immutable Secrets and ConfigMaps
    
    Registered: Fri Dec 26 09:05:12 UTC 2025
    - Last Modified: Fri Oct 14 07:03:14 UTC 2022
    - 367.3K bytes
    - Viewed (0)
  7. helm-releases/minio-5.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: Sat Sep 30 20:46:10 UTC 2023
    - 20.6K bytes
    - Viewed (0)
  8. helm-releases/minio-5.0.15.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 Jan 12 18:18:57 UTC 2024
    - 20.8K bytes
    - Viewed (0)
  9. helm-releases/minio-5.0.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: Mon Dec 19 08:53:02 UTC 2022
    - 20.3K bytes
    - Viewed (0)
  10. helm-releases/minio-5.0.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 23 20:29:40 UTC 2022
    - 20.3K bytes
    - Viewed (0)
Back to top