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:...

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...

``` 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....

    assertThat(b.code).isEqualTo(200)
    assertThat(server.takeRequest().exchangeIndex).isEqualTo(0)
    assertThat(
      server.takeRequest().exchangeIndex,
      "When connection: close is used, each request should get its own connection",
    ).isEqualTo(0)
  }

  @Test
  fun connectionCloseInResponse() {
    server.enqueue(MockResponse(headers = headersOf("Connection", "close")))

    @Resource
    protected MimeTypeHelper mimeTypeHelper;

    /** The HTTP client instance */
    protected volatile CloseableHttpClient httpClient;

    /** List of request headers to be sent with each request */
    private final List<Header> requestHeaderList = new ArrayList<>();

    /** Map of HTTP client properties */
    private final Map<String, Object> httpClientPropertyMap = new HashMap<>();

          def extraFipsJars = configurations.detachedConfiguration(bcFips, bcTlsFips)
          testClusters.configureEach {
            extraFipsJars.files.each {
              extraJarFile it
            }
          }
        }
        tasks.withType(TestClustersAware).configureEach {
          dependsOn 'fipsResources'
        }
        testClusters.configureEach {

    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

- Kube-proxy health check ports used to listen to `:<port>` for each of the services. This is not needed and opens ports in addresses the cluster user may not have intended. The PR limits listening to all node address which are controlled by `--nodeport-addresses` flag. if no addresses are provided then we default to existing behavior by listening to `:<port>` for each service ([#104742](https://github.com/kubernetes/kubernetes/pull/104742), [@khenidak](https://github.com/khenidak))...

``` 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....