the account 'default' will be used. serviceAccount: create: true ## The name of the service account to use. If 'create' is 'true', a service account with that name ## will be created. name: "minio-sa" metrics: serviceMonitor: enabled: false # scrape each node/pod individually for additional metrics includeNode: false public: true additionalLabels: {} annotations: {} # for node metrics relabelConfigs: {} # for cluster metrics relabelConfigsCluste: {} # metricRelabelings: # - regex: (server|pod) # action:...

    assertThat(response.body.string()).isEqualTo("abc")
    response.body.close()
    assertThat(eventRecorder.recordedEventTypes()).isNotEmpty()
  }

  /**
   * Returns a map with sample values for each possible parameter of an [EventListener] function
   * parameter.
   */
  private fun sampleValuesMap(): Map<Class<*>, Any> {
    TestValueFactory().use { factory ->
      val address = factory.newAddress("a")

SetIV(iv []byte) { if len(iv) != len(x.iv) { panic("cipher: incorrect length IV") } copy(x.iv[:], iv) } func cryptBlocksDecGeneri(b *Block, civ *[BlockSize]byte, dst, src []byte) { // For each block, we need to xor the decrypted data with the previous // block's ciphertext (the iv). To avoid making a copy each time, we loop // over the blocks backwards. end := len(src) start := end - BlockSize prev := start - BlockSize // Copy the last block of ciphertext as the IV of the next call. iv := *civ copy(civ[:],...

	{"a.RegExp*", ".(|)*+?^$[]", 8},
	{dots + dots + dots, " ", -1},
	{"012abcba210", "\xffb", 6},
	{"012\x80bcb\x80210", "\xffb", 7},
	{"0123456\xcf\x80abc", "\xcfb\x80", 10},
}

// Execute f on each test case.  funcName should be the name of f; it's used
// in failure reports.
func runIndexTests(t *testing.T, f func(s, sep []byte) int, funcName string, testCases []BinOpTest) {
	for _, test := range testCases {

the account 'default' will be used. serviceAccount: create: true ## The name of the service account to use. If 'create' is 'true', a service account with that name ## will be created. name: "minio-sa" metrics: serviceMonitor: enabled: false # scrape each node/pod individually for additional metrics includeNode: false public: true additionalLabels: {} # for node metrics relabelConfigs: {} # for cluster metrics relabelConfigsCluste: {} # metricRelabelings: # - regex: (server|pod) # action: labeldrop...

- Added driver-owned fields in `ResourceSlice` to mark whether the device was shareable among multiple resource claims (or requests) and to specify how each capacity could be shared between different requests.
  - Added user-owned fields in `ResourceClaim` to specify resource requirements against each device capacity.
  - Added scheduler-owned field in `ResourceClaim.Status` to specify how much device capacity is reserved for a specific request.

    if (pathNotFound != null) {
      throw pathNotFound;
    }
    // TODO(cgdecker): Should there be a custom exception type for this?
    // Also, should we try to include the Path of each file we may have failed to delete rather
    // than just the exceptions that occurred?
    FileSystemException deleteFailed =
        new FileSystemException(
            path.toString(),
            null,

  2. Start single node server with 64 local drives "/mnt/data1" to "/mnt/data64".
     {{.Prompt}} {{.HelpName}} /mnt/data{1...64}

  3. Start distributed MinIO server on an 32 node setup with 32 drives each, run following command on all the nodes
     {{.Prompt}} {{.HelpName}} http://node{1...32}.example.com/mnt/export{1...32}

  4. Start distributed MinIO server in an expanded setup, run the following command on all the nodes

the account 'default' will be used. serviceAccount: create: true ## The name of the service account to use. If 'create' is 'true', a service account with that name ## will be created. name: "minio-sa" metrics: serviceMonitor: enabled: false # scrape each node/pod individually for additional metrics includeNode: false public: true additionalLabels: {} annotations: {} # for node metrics relabelConfigs: {} # for cluster metrics relabelConfigsCluste: {} # metricRelabelings: # - regex: (server|pod) # action:...

``` 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 each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume....