@@ -19,9 +19,9 @@ Please refer to the Slate user documentation (link coming soon) if you have any
### Helm Chart directory/file structure
A [Chart](https://helm.sh/docs/topics/charts/) is organized as a collection of files inside a directory. The directory name is the name of the chart. You can see all of the example application charts in this repositories charts/ directory.
A [Chart](https://helm.sh/docs/topics/charts/) is organized as a collection of files inside a directory. The directory name, within the charts/ directory, is the name of the chart. So, you can see all of the example application charts in this repositories charts/ directory.
Here is the overall structure, of simple chart, using minio-standalone as an example:
Here is the overall structure of a simple helm chart, using minio-standalone in this repository, as an example:
@@ -29,3 +29,24 @@ This example uses these core components of Kubernetes:
In the following we will create the pieces of our Minio Standalone application, that use the above core components.
### Create the Persistent Volume Claim
Minio needs persistent storage to store objects. Without persistent storage, the data stored in an application instance will be stored in the container file system, which will be destroyed as soon as the container restarts. This is true for any application needing to persist data on Slate. So, to persist data in your application, use a persistent volume claim, or "PVC".
The file we use to do this is [minio-standalone-pvc.yaml](https://code.ornl.gov/ryu/slate_helm_examples/-/blob/prout-dev/charts/minio-standalone/templates/minio-standalone-pvc.yaml):
```
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
# This name uniquely identifies the PVC. This is used in deployment.
name: minio-standalone-pv-claim
spec:
# Read more about access modes here: http://kubernetes.io/docs/user-guide/persistent-volumes/#access-modes
accessModes:
# The volume is mounted as read-write by a single node
- ReadWriteOnce
resources:
# This is the request for storage. Should be available in the cluster.