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. ### Installing the Chart (toy-setup) Minimal toy setup for testing purposes can be deployed using: ```bash helm install --set resources.requests.memory=512Mi...

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. ### Installing the Chart (toy-setup) Minimal toy setup for testing purposes can be deployed using: ```bash helm install --set resources.requests.memory=512Mi...

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. ### Installing the Chart (toy-setup) Minimal toy setup for testing purposes can be deployed using: ```bash helm install --set resources.requests.memory=512Mi...

    @Test
    public void test_create_searchLogEnabled() {
        // Test configuration for search log creation
        SuggestCreator.Options options = new SuggestCreator.Options();
        assertNotNull(options);
    }

    // Test create with documents enabled
    @Test
    public void test_create_documentsEnabled() {
        // Test configuration for document creation

        response.reset();
        assertTrue(response.hasMoreElements());
    }

    @Test
    @DisplayName("Verify Configuration is passed to parent")
    void testConfigurationPassedToParent() {
        // Arrange
        Configuration testConfig = mock(Configuration.class);

        // Act
        TransPeekNamedPipeResponse testResponse = new TransPeekNamedPipeResponse(testConfig);

        // Assert

                configProps.put("aether.transport.wagon.config." + server.getId(), config);

                // Translate to proper resolver configuration properties as well (as Plexus XML above is Wagon specific
                // only) but support only configuration/httpConfiguration/all, see
                // https://maven.apache.org/guides/mini/guide-http-settings.html
                Map<String, String> headers = null;

    private boolean directory;
    private boolean isExtended;

    /**
     * Constructs an NT Create AndX response.
     *
     * @param config the configuration
     */
    public SmbComNTCreateAndXResponse(final Configuration config) {
        super(config);
    }

    /**
     * Gets the file type.
     *
     * @return the fileType
     */
    public final int getFileType() {

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

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

    // can be passed back so that the default configuration information can be populated.
    //
    // We need to know the specific version so that we can look up the right version of the plugin descriptor
    // which tells us what the default configuration is.
    //

    /**