Commit 2faaf940 authored by Prout, Ryan's avatar Prout, Ryan
Browse files

update readme

parent 99ff8bb8
Loading
Loading
Loading
Loading
+2 −102
Original line number Diff line number Diff line
@@ -220,7 +220,7 @@ spec:

### The Values File

Helm templates provide built-in objects. One of these objects is "Values". This object provides access to values passed into the chart. The contents, in this case, come from [values.yaml](https://code.ornl.gov/ryu/slate_helm_examples/-/blob/prout-dev/charts/minio-standalone/values.yaml):
Helm templates provide built-in objects. One of these objects is "Values". This object provides access to values passed into the chart. The contents, in this case, come from [values.yaml](./values.yaml):

```
# This can be used to provide variables to your chart. 
@@ -237,103 +237,3 @@ minio:
```

**NOTE**: Please make sure you rename your ```minio.host``` value. This needs to be unique.
 No newline at end of file

## Installing the Chart

### Log into Marble


Log into Slate's Marble cluster with the OC CLI Tool.
```
oc login https://api.marble.ccs.ornl.gov
```

You should see a response similar to this, seeing your available project namespace(s):
```
Login successful.

You have one project on this server: "stf007"

Using project "stf007".
```
### Create secret token (do not keep this in a repo, only locally)

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:

```
apiVersion: v1
kind: List
metadata: {}
items:
- apiVersion: v1
  kind: Secret
  metadata:
    name: minio-standalone-access-key
  stringData:
    SECRET_TOKEN: <your_choice>
- apiVersion: v1
  kind: Secret
  metadata:
    name: minio-standalone-secret-key
  stringData:
    SECRET_TOKEN: <your_choice>
```
Replace ```<your_choice>``` with your secret access tokens of choice. These are needed to log into the MinIO GUI.

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

```
git clone https://code.ornl.gov/ryu/slate_helm_examples.git && cd slate_helm_examples/charts
```

### Check Helm works

Run simple Helm command to make sure it works properly (assuming the use of helm3):

```
helm ls
```

Output will be similar, depending on if you have any existing applications (may be empty):

```
NAME                              NAMESPACE REVISION  UPDATED                               STATUS    CHART                   APP VERSION
gitlab-runner-for-slate-examples  stf007    9         2020-05-18 11:31:08.3245 -0400 EDT    deployed  gitlab-runner-0.16.1    12.10.2    
minio-standalone                  stf007    4         2020-05-19 13:00:38.165911 -0400 EDT  deployed  minio-standalone-1.0.0
```

### Use Helm to install MinIO Standalone

Use helm to install the application into your namespace/project with a unique name:

```
helm install <your-uid>-minio-standalone minio-standalone/ --namespace <your_namespace>
```

**NOTE:** ```<your_namespace>``` is available above, from the login output, or you can run ```oc get projects``` to list your projects/namespaces.

Check your deployment:

```
helm ls
```

Log into the Marble GUI to see all the pieces there too: https://console-openshift-console.apps.marble.ccs.ornl.gov/

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