- "9001:9001"
    depends_on:
      - minio1
      - minio2
      - minio3
      - minio4

## By default this config uses default local driver,
## For custom volumes replace with volume driver configuration.
volumes:
  data1-1:
  data1-2:
  data1-3:
  data1-4:
  data1-5:
  data1-6:
  data1-7:
  data1-8:

  data2-1:
  data2-2:
  data2-3:
  data2-4:
  data2-5:
  data2-6:

//
//	{
//	  "xAmzRequestId": "a2871150-1df5-4dc9-ad9f-3da283ca1bf3",
//	  "getObjectContext": {
//	    "outputRoute": "...",
//	    "outputToken": "...",
//	    "inputS3Url": "<presignedURL>"
//	  },
//	  "configuration": { // not useful in MinIO
//	    "accessPointArn": "...",
//	    "supportingAccessPointArn": "...",
//	    "payload": ""
//	  },
//	  "userRequest": {
//	    "url": "...",
//	    "headers": {

Installing the Chart Install this chart using: ```bash helm install --namespace minio --set rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. ### Upgrading the Chart You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using...

import org.junit.jupiter.params.provider.CsvSource;
import org.junit.jupiter.params.provider.ValueSource;
import org.mockito.Mock;
import org.mockito.MockitoAnnotations;

import jcifs.CIFSContext;
import jcifs.Configuration;
import jcifs.internal.smb2.RequestWithFileId;
import jcifs.internal.smb2.ServerMessageBlock2Request;
import jcifs.internal.smb2.Smb2Constants;
import jcifs.internal.util.SMBUtil;

/**

     * @return the create request configured for reconnection
     */
    protected Smb2CreateRequest createReconnectionRequest(HandleInfo info) {
        // This would need access to the Configuration and proper setup
        // For now, we provide the structure

        // Smb2CreateRequest request = new Smb2CreateRequest(config, info.getPath());

In 12 drive example above, with MinIO server running in the default configuration, you can lose any of the six drives and still reconstruct the data reliably from the remaining drives.

## Why is Erasure Code useful?

                consumeArchive {}
                consumeDir {}
            }

            dependencies {
                consumeDir project(path: ':producer-tar', configuration:'extracted')
                consumeArchive project(path: ':producer-tar', configuration:'default' )
            }

            tasks.register("copyDir", Copy) {
                from(configurations.consumeDir)
                into('build/dir')

- Windows Server test environment with:
  - Failover clustering
  - RDMA-capable network adapters
  - DFS namespace
  - Multiple network interfaces

## Configuration Properties

```properties
# Lease configuration
jcifs.smb.client.useLeases=true
jcifs.smb.client.leaseTimeout=30000

# Persistent handles
jcifs.smb.client.usePersistentHandles=true
jcifs.smb.client.durableTimeout=120000

        lenient().when(response.getOutputStream()).thenReturn(servletOutputStream);
    }

    @Test
    void testInit_success() throws ServletException {
        // Test successful initialization with valid configuration
        Map<String, String> initParams = new HashMap<>();
        initParams.put("jcifs.smb.client.domain", "TEST_DOMAIN");
        initParams.put("jcifs.http.domainController", "dc.test.com");

import org.mockito.Mock;
import org.mockito.MockitoAnnotations;

import jcifs.Configuration;
import jcifs.internal.SMBProtocolDecodingException;
import jcifs.internal.util.SMBUtil;
import jcifs.smb.NtStatus;

class Smb2EchoResponseTest {

    @Mock
    private Configuration mockConfig;

    @Mock
    private Smb2SigningDigest mockDigest;

    private Smb2EchoResponse echoResponse;