Search Options

Results per page
Sort
Preferred Languages
Advance

Results 211 - 220 of 250 for comandos (0.05 sec)

  1. helm-releases/minio-3.4.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 Dec 19 22:32:49 UTC 2021
    - 14.8K bytes
    - Viewed (0)
  2. helm-releases/minio-3.4.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: Mon Dec 20 21:11:50 UTC 2021
    - 15.2K bytes
    - Viewed (0)
  3. CHANGELOG/CHANGELOG-1.29.md

    A security vulnerability has been discovered in Kubernetes windows nodes
    that could allow a user with the ability to query a node's '/logs' endpoint
    to execute arbitrary commands on the host.
    
    **Affected Versions**:
      - kubelet <= v1.29.12
      - kubelet <= v1.30.8
      - kubelet <= v1.31.4
      - kubelet = v1.32.0
    
    **Fixed Versions**:
      - kubelet 1.29.13
      - kubelet 1.30.9
    Registered: Fri Dec 26 09:05:12 UTC 2025
    - Last Modified: Wed Mar 12 00:36:01 UTC 2025
    - 429.6K bytes
    - Viewed (1)
  4. helm-releases/minio-1.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: Fri Aug 20 22:30:54 UTC 2021
    - 13.5K bytes
    - Viewed (0)
  5. helm-releases/minio-1.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: Fri Aug 20 22:32:29 UTC 2021
    - 13.5K bytes
    - Viewed (0)
  6. helm-releases/minio-1.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: Tue Aug 24 19:04:07 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  7. helm-releases/minio-1.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: Wed Aug 25 02:12:51 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  8. helm-releases/minio-1.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: Wed Aug 25 19:53:57 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  9. helm-releases/minio-2.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: Thu Aug 26 07:36:46 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  10. CHANGELOG/CHANGELOG-1.31.md

    A security vulnerability has been discovered in Kubernetes windows nodes
    that could allow a user with the ability to query a node's '/logs' endpoint
    to execute arbitrary commands on the host.
    
    **Affected Versions**:
      - kubelet <= v1.29.12
      - kubelet <= v1.30.8
      - kubelet <= v1.31.4
      - kubelet = v1.32.0
    
    **Fixed Versions**:
      - kubelet 1.29.13
    Registered: Fri Dec 26 09:05:12 UTC 2025
    - Last Modified: Wed Nov 12 11:33:21 UTC 2025
    - 451.9K bytes
    - Viewed (0)
Back to top