update readme

```

### Create secret token (do not keep this in a repo, only locally)

One thing we need to do is create the username and password for MinIO as environment secrets. To avoid keeping the secret-tokens.yaml file in the public repository, we will quickly creat that manually here and install it in your namespace.

One thing we need to do is create the access key and secret key for the MinIO deployment. To avoid keeping the secret-tokens.yaml file in the public repository, we will quickly create those now.

Example secret-token.yaml file:

  stringData:

    SECRET_TOKEN: <your_choice>

```

Replace ```<your_choice>``` with your secret tokens of choice. These map to username and passowrd respectively, when you get to the MinIO GUI.

Replace ```<your_choice>``` with your secret access tokens of choice. These are needed to log into the MinIO GUI.

Once you have your tokens in there, you can apply it like this:

Once you have your secret-tokens.yaml file established, you can apply it like this:

```

oc apply -f secret-token.yaml

```

The [minio-standalone-deployment.yaml](https://code.ornl.gov/ryu/slate_helm_examples/-/blob/master/charts/minio-standalone/templates/minio-standalone-deployment.yaml) file picks these up as environment variables.

### Clone this repo

Clone the repo to your local system. Then, 'cd' into 'slate_helm_examples/charts'.

MinIO will take several minutes to spin up, but after a few minutes you will be able to access your MinIO applicaiton at: 

```https://<your_UID>-minio-standalone.apps.marble.ccs.ornl.gov/minio/```

### Use Helm to Delete the MinIO Standalone Deployment

```helm delete minio-standalone```