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

### Installing the Chart (toy-setup)

Minimal toy setup for testing purposes can be deployed using:

```bash

import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;

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

@ExtendWith(MockitoExtension.class)
class Smb2LogoffRequestTest {

    @Mock
    Configuration configuration;

    @Mock
    CIFSContext cifsContext;

    // Helper to create a fresh request under test

     */
    public SearchForm() {
    }

    /**
     * The name field for searching file configurations.
     */
    public String name;

    /**
     * The paths field for searching file configurations.
     */
    public String paths;

    /**
     * The description field for searching file configurations.
     */
    public String description;

     */
    public SearchForm() {
    }

    /**
     * The name field for searching web configurations.
     */
    public String name;

    /**
     * The URLs field for searching web configurations.
     */
    public String urls;

    /**
     * The description field for searching web configurations.
     */
    public String description;

	"io"
	"sort"
	"strconv"
	"strings"
)

var (
	errReplicationTooManyRules          = Errorf("Replication configuration allows a maximum of 1000 rules")
	errReplicationNoRule                = Errorf("Replication configuration should have at least one rule")
	errReplicationUniquePriority        = Errorf("Replication configuration has duplicate priority")

     * @throws CIFSException if an error occurs during cleanup
     */
    boolean close() throws CIFSException;

    /**
     * Get the configuration object for this context
     *
     * @return the active configuration
     */
    Configuration getConfig();

    /**
     * Get the name service client for NetBIOS name resolution
     *
     * @return the name server client
     */

 *
 */
public class Smb2LogoffResponse extends ServerMessageBlock2Response {

    /**
     * Constructs an SMB2 logoff response with the given configuration.
     *
     * @param config the configuration for this response
     */
    public Smb2LogoffResponse(final Configuration config) {
        super(config);
    }

    /**
     * {@inheritDoc}
     *

    /**
     * Constructs an empty write AndX request.
     *
     * @param config the configuration to use
     */
    public SmbComWriteAndX(final Configuration config) {
        super(config, SMB_COM_WRITE_ANDX, null);
    }

    /**
     * Constructs a write AndX request to write data to a file.
     *
     * @param config the configuration to use
     * @param fid the file identifier

## FAQ

> Why is this change needed?

Before, there were two separate mechanisms - S3 objects got encrypted using a KMS,
if present, and the IAM / configuration data got encrypted with the root credentials.
Now, MinIO encrypts IAM / configuration and S3 objects with a KMS, if present. This

package projects

import common.HIDDEN_ARTIFACT_DESTINATION
import common.cleanupRule
import common.isSecurityFork
import configurations.BaseGradleBuildType
import configurations.GitHubMergeQueueCheckPass
import configurations.PerformanceTestsPass
import configurations.StageTriggers
import jetbrains.buildServer.configs.kotlin.ParameterDisplay
import jetbrains.buildServer.configs.kotlin.Project
import model.CIBuildModel