return env.Get("KUBERNETES_SERVICE_HOST", "") != ""
}

// IsBOSH returns true if minio is deployed from a bosh package
func IsBOSH() bool {
	// "/var/vcap/bosh" exists in BOSH deployed instance.
	_, err := os.Stat("/var/vcap/bosh")
	if osIsNotExist(err) {
		return false
	}

	// Log error, as we will not propagate it to caller

            } catch (ArtifactNotFoundException anfe) {
                // These are cases where the artifact just isn't present in any of the remote repositories
                // because it wasn't deployed, or it was deployed in the wrong place.

                synchronized (result) {
                    result.addMissingArtifact(artifact);
                }
            } catch (ArtifactResolutionException e) {

```

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

      <fields>
        <field>
          <name>timestamp</name>
          <version>1.0.0+</version>
          <description>The timestamp when this version was deployed. The timestamp is expressed using UTC in the format yyyyMMdd.HHmmss.</description>
          <type>String</type>
        </field>
        <field>
          <name>buildNumber</name>
          <version>1.0.0+</version>

     */
    @Config(type = "java.lang.Integer")
    public static final String MAVEN_DEPLOY_SNAPSHOT_BUILD_NUMBER = "maven.deploy.snapshot.buildNumber";

    /**
     * User property for controlling whether build POMs are deployed alongside consumer POMs.
     * When set to <code>false</code>, only the consumer POM will be deployed, and the build POM
     * will be excluded from deployment. This is useful to avoid deploying internal build information

##
runtimeClassName: ""

## Set default rootUser, rootPassword
## rootUser and rootPassword is generated when not set
## Distributed MinIO ref: https://docs.min.io/community/minio-object-store/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html
##
rootUser: ""
rootPassword: ""

## Use existing Secret that store following variables:
##
## | Chart var             | .data.<key> in Secret    |

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

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

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

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