Search Options

Results per page
Sort
Preferred Languages
Advance

Results 41 - 50 of 165 for yams (0.01 sec)

  1. helm-releases/minio-3.0.2.tgz

    command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Sep 03 08:11:32 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  2. helm-releases/minio-1.0.2.tgz

    command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 24 18:58:05 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  3. cmd/batch-replicate_test.go

    `
    	var job BatchJobRequest
    	err := yaml.Unmarshal([]byte(replicateYaml), &job)
    	if err != nil {
    		t.Fatal("Failed to parse batch-job-replicate yaml", err)
    	}
    	if !slices.Equal(job.Replicate.Source.Prefix.F(), []string{"object-prefix1"}) {
    		t.Fatal("Failed to parse batch-job-replicate yaml", err)
    	}
    	multiPrefixReplicateYaml := `
    replicate:
      apiVersion: v1
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Aug 01 12:53:30 UTC 2024
    - 7.9K bytes
    - Viewed (0)
  4. helm-releases/minio-3.0.0.tgz

    command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Sep 02 01:47:43 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  5. docs/distributed/CONFIG.md

    ## MinIO configuration YAML
    
    MinIO now supports starting the server arguments and configuration via a YAML configuration file. This YAML configuration describes everything that can be configured in a MinIO setup, such as '--address', '--console-address' and command line arguments for the MinIO server.
    
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Jun 25 02:30:18 UTC 2024
    - 4.2K bytes
    - Viewed (0)
  6. helm-releases/minio-2.0.1.tgz

    command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 31 09:09:09 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  7. docs/tls/kubernetes/README.md

    kubectl get secrets
    ```
    
    You should see a secret named `tls-ssl-minio`.
    
    ## 3. Update deployment yaml file
    
    Whether you are planning to use Kubernetes StatefulSet or Kubernetes Deployment, the steps remain the same.
    
    If you're using certificates provided by a CA, add the below section in your yaml file under `spec.volumes[]`
    
    ```yaml
        volumes:
          - name: secret-volume
            secret:
              secretName: tls-ssl-minio
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 12 18:20:36 UTC 2025
    - 3K bytes
    - Viewed (0)
  8. cmd/batch-rotate.go

    type BatchKeyRotateFilter struct {
    	NewerThan     time.Duration `yaml:"newerThan,omitempty" json:"newerThan"`
    	OlderThan     time.Duration `yaml:"olderThan,omitempty" json:"olderThan"`
    	CreatedAfter  time.Time     `yaml:"createdAfter,omitempty" json:"createdAfter"`
    	CreatedBefore time.Time     `yaml:"createdBefore,omitempty" json:"createdBefore"`
    	Tags          []BatchJobKV  `yaml:"tags,omitempty" json:"tags"`
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Aug 29 02:39:48 UTC 2025
    - 14.7K bytes
    - Viewed (0)
  9. .github/workflows/multipart/docker-compose-site2.yaml

    Harshavardhana <******@****.***> 1696068836 -0700
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Sat Sep 30 10:13:56 UTC 2023
    - 1.5K bytes
    - Viewed (0)
  10. .github/workflows/run-mint.sh

    docker pull docker.io/minio/mint:edge
    
    docker-compose -f minio-${MODE}.yaml up -d
    sleep 1m
    
    docker system prune -f || true
    docker volume prune -f || true
    docker volume rm $(docker volume ls -q -f dangling=true) || true
    
    # Stop two nodes, one of each pool, to check that all S3 calls work while quorum is still there
    [ "${MODE}" == "pools" ] && docker-compose -f minio-${MODE}.yaml stop minio2
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Mon Jan 20 14:49:07 UTC 2025
    - 1.9K bytes
    - Viewed (0)
Back to top