Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 41 - 50 of 129 for kubectl (0.11 seconds)

  1. helm-releases/minio-5.0.6.tgz

    .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 forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Mon Feb 13 06:53:06 GMT 2023
    - 20.3K bytes
    - Click Count (0)
  2. helm-releases/minio-4.0.11.tgz

    .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 forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Sun Aug 07 05:41:47 GMT 2022
    - 19.2K bytes
    - Click Count (0)
  3. helm-releases/minio-4.0.2.tgz

    .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 forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Mon May 09 04:25:47 GMT 2022
    - 18K bytes
    - Click Count (0)
  4. helm-releases/minio-4.0.3.tgz

    .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 forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Fri Jul 08 06:16:22 GMT 2022
    - 18K bytes
    - Click Count (0)
  5. helm-releases/minio-5.0.0.tgz

    .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 forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Tue Oct 25 10:20:22 GMT 2022
    - 19.8K bytes
    - Click Count (0)
  6. helm-releases/minio-3.6.4.tgz

    .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 forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Tue Apr 12 01:30:28 GMT 2022
    - 17.9K bytes
    - Click Count (0)
  7. CHANGELOG/CHANGELOG-1.5.md

    1. Export existing PodSecurityPolicy objects:
      * `kubectl get podsecuritypolicies -o yaml > psp.yaml`
    2. Review and delete any PodSecurityPolicy objects you do not want all pod-creating users to be able to use (NOTE: Privileged users that were making use of those policies will also lose access to those policies). For example:
      * `kubectl delete podsecuritypolicies/my-privileged-policy`
    Created: Fri Dec 26 09:05:12 GMT 2025
    - Last Modified: Thu Dec 24 02:28:26 GMT 2020
    - 136.4K bytes
    - Click Count (0)
  8. docs/distributed/DECOMMISSION.md

    - On Operator based MinIO deployments, you need to modify the `tenant.yaml` specification and modify the `pools:` section from two entries to a single entry. After making relevant changes, proceed to execute `kubectl apply -f tenant.yaml`.
    
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Mon Jul 11 14:59:49 GMT 2022
    - 8.3K bytes
    - Click Count (0)
  9. helm-releases/minio-5.4.0.tgz

    }}.{{ .Values.clusterDomain }} 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 forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Fri Jan 03 05:34:47 GMT 2025
    - 21.7K bytes
    - Click Count (0)
  10. CHANGELOG/CHANGELOG-1.13.md

    mostly focused on stabilizing the items we’ve been working on over the past releases such as server-side printing and its support in kubectl, as well as finishing [kubectl diff which is based on server-side dry-run feature](https://kubernetes.io/docs/concepts/overview/working-with-objects/object-management/#how-to-create-objects). We’ve continued separating kubectl code to prepare for extraction out of main repository. Finally, thanks to the awesome support and feedback from community we’ve managed...
    Created: Fri Dec 26 09:05:12 GMT 2025
    - Last Modified: Thu May 05 13:44:43 GMT 2022
    - 273.1K bytes
    - Click Count (0)
Back to Top