Search Options

Results per page
Sort
Preferred Languages
Advance

Results 21 - 30 of 664 for xport (0.08 sec)

  1. helm-releases/minio-3.6.4.tgz

    .Values.service.type "ClusterIP" "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 }}...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Apr 12 01:30:28 UTC 2022
    - 17.9K bytes
    - Viewed (0)
  2. docs/multi-tenancy/README.md

    ```sh
    export MINIO_ROOT_USER=<TENANT1_ACCESS_KEY>
    export MINIO_ROOT_PASSWORD=<TENANT1_SECRET_KEY>
    minio server --address :9001 http://192.168.10.1{1...4}/data/tenant1
    
    export MINIO_ROOT_USER=<TENANT2_ACCESS_KEY>
    export MINIO_ROOT_PASSWORD=<TENANT2_SECRET_KEY>
    minio server --address :9002 http://192.168.10.1{1...4}/data/tenant2
    
    export MINIO_ROOT_USER=<TENANT3_ACCESS_KEY>
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Aug 12 18:20:36 UTC 2025
    - 3.1K bytes
    - Viewed (0)
  3. helm-releases/minio-3.2.0.tgz

    .Values.service.type "ClusterIP" "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 }}...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Wed Oct 13 02:16:24 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  4. helm-releases/minio-3.4.0.tgz

    .Values.service.type "ClusterIP" "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 }}...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Dec 19 22:32:49 UTC 2021
    - 14.8K bytes
    - Viewed (0)
  5. helm-releases/minio-3.4.1.tgz

    .Values.service.type "ClusterIP" "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 }}...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Mon Dec 20 21:11:50 UTC 2021
    - 15.2K bytes
    - Viewed (0)
  6. helm-releases/minio-3.3.3.tgz

    .Values.service.type "ClusterIP" "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 }}...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sat Dec 11 17:28:02 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  7. helm-releases/minio-3.4.7.tgz

    .Values.service.type "ClusterIP" "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 }}...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Jan 25 20:49:24 UTC 2022
    - 15.2K bytes
    - Viewed (0)
  8. helm-releases/minio-4.0.13.tgz

    ## Additional volumes to minio container extraVolumes: [] ## Additional volumeMounts to minio container extraVolumeMounts: [] ## Internal port number for MinIO S3 API container ## Change service.port to change external port number minioAPIPort: "9000" ## Internal port number for MinIO Browser Console container ## Change consoleService.port to change external port number minioConsolePort: "9001" ## Update strategy for Deployments DeploymentUpdate: type: RollingUpdate maxUnavailable: 0 maxSurge: 100%...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Aug 23 18:18:14 UTC 2022
    - 19.5K bytes
    - Viewed (0)
  9. helm-releases/minio-4.0.5.tgz

    "true" to disable this behaviour. ignoreChartChecksums: false ## Additional arguments to pass to minio binary extraArgs: [] ## Internal port number for MinIO S3 API container ## Change service.port to change external port number minioAPIPort: "9000" ## Internal port number for MinIO Browser Console container ## Change consoleService.port to change external port number minioConsolePort: "9001" ## Update strategy for Deployments DeploymentUpdate: type: RollingUpdate maxUnavailable: 0 maxSurge: 100%...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sat Jul 16 06:42:56 UTC 2022
    - 18.3K bytes
    - Viewed (0)
  10. helm-releases/minio-4.0.8.tgz

    "true" to disable this behaviour. ignoreChartChecksums: false ## Additional arguments to pass to minio binary extraArgs: [] ## Internal port number for MinIO S3 API container ## Change service.port to change external port number minioAPIPort: "9000" ## Internal port number for MinIO Browser Console container ## Change consoleService.port to change external port number minioConsolePort: "9001" ## Update strategy for Deployments DeploymentUpdate: type: RollingUpdate maxUnavailable: 0 maxSurge: 100%...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Jul 29 23:39:54 UTC 2022
    - 18.6K bytes
    - Viewed (0)
Back to top