--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 the command: ```bash helm get values my-release > old_values.yaml ``` Then change...

--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 the command: ```bash helm get values my-release > old_values.yaml ``` Then change...

--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 the command: ```bash helm get values my-release > old_values.yaml ``` Then change...

                            null,
                            "Failed to interpolate profile activation property " + s + ": " + propertyName
                                    + " expressions are not supported during profile activation.",
                            locationSupplier.get());
                }
            }
        };
        Optional<Activation> root = Optional.of(activation);

 *
 * This is because those two hosts share the same IP address. This is an old, bad design decision
 * that makes `java.net.URL` unusable for many things. It shouldn't be used as a [Map] key or in a
 * [Set]. Doing so is both inefficient because equality may require a DNS lookup, and incorrect
 * because unequal URLs may be equal because of how they are hosted.
 *
 * ### Equal URLs should be equal
 *

		isDecommissioned := z.poolMeta.isBucketDecommissioned(idx, bucket.String())
		z.poolMetaMutex.RUnlock()
		if isDecommissioned {
			if serverDebugLog {
				console.Debugln("decommission: already done, moving on", bucket)
			}

			z.poolMetaMutex.Lock()
			if z.poolMeta.BucketDone(idx, bucket) {
				// remove from pendingBuckets and persist.
				decomLogIf(ctx, z.poolMeta.save(ctx, z.serverPools))
			}

                    this.socket.close();
                } catch (final IOException ioe) {
                    log.debug("Failed to close socket", ioe);
                }
                throw new SmbException("EOF during NetBIOS session request");
            }
            switch (this.sbuf[0] & 0xFF) {
            case SessionServicePacket.POSITIVE_SESSION_RESPONSE:
                if (log.isDebugEnabled()) {

  }

  /**
   * When callers parse a URL with query components that aren't encoded, we shouldn't convert them
   * into a canonical form because doing so could be semantically different.
   */
  @Test
  fun queryCharactersNotReencodedWhenParsed() {
    val url = parse("http://host/?a=!$(),/:;?@[]\\^`{|}~")

--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 the command: ```bash helm get values my-release > old_values.yaml ``` Then change...

--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 --set replicas=1 --set persistence.enabled=false --set mode=standalone --set...