StorageOS and Kubernetes by storageos

Install StorageOS

In this tutorial, we'll look how to install the StorageOS Cluster Operator. It is a Kubernetes native application developed to deploy and configure StorageOS clusters, and assist with maintenance operations. The operator will deploy a StorageOS cluster based on the configuration specified in the cluster definition.

First we need to install the StorageOS operator using the following yaml manifest.

kubectl create -f https://github.com/storageos/cluster-operator/releases/download/1.5.0/storageos-operator.yaml

Verify the Cluster Operator pod status

kubectl -n storageos-operator get pod -w

The READY 1/1 indicates that storageoscluster resources can be created. Press Ctrl+C to continue once the pod is up.

Create a Secret defining the StorageOS API Username and Password.

kubectl create -f storageos-secret.yaml

StorageOS Installation.

kubectl create -f storageos-cluster.yaml

Verify StorageOS Installation.

kubectl -n storageos get pods -w

The above command watches the pods created by the Cluster Definition example. Note that pods typically take approximately 65 seconds to enter the Running Phase. Press Ctrl+C to continue once the pods are up.

Moreover, you can see more information about the StorageOS Cluster.

kubectl -n storageos-operator describe storageoscluster

You can also verify that StorageOS was installed succesfully using the StorageOS CLI.

storageos node ls

Storage Class

In this tutorial, we'll look at how you dynamically provision storage using StorageOS.

An administrator can create a Storage Class to describe the storage that can be provisioned.

Create fast001 StorageClass:

kubectl create -f storageos-storageclass.yaml

The fast001 StorageClass should be backed by the kubernetes.io/storageos provisioner:

kubectl describe storageclass fast001

Persistent Volume

Developers can request storage using persistent volume claims. In order to demonstrate this we will deploy a Redis Server on Kubernetes (as Redis can persist its state to a persistent volume) with the data being written to a StorageOS persistent volume.

Create PersistentVolumeClaim and a Redis pod which references the fast001 StorageClass:

kubectl create -f storageos-pvc.yaml

kubectl create -f redis-pod.yaml

You should see a StorageOS persistent volume:

kubectl describe pv

Usually takes ~30 seconds to come up after it's been created.

Confirm StorageOS provisioned the volume:

storageos volume ls --format "table {{.Name}}\t{{.Size}}\t{{.Location}}"

The link between the PersistentVolumeClaim and the pod comes from the pod referencing the PersistentVolumeClaim in the pods yaml definition.

Run the following command to see the redis-pod definition.

cat redis-pod.yaml

You can see that the PersistentVolumeClaim claimName has been set to redispvc.

Run the following command to see the PersistentVolumeClaim definition.

cat storageos-pvc.yaml

Notice that the PersistentVolumeClaim name is redispvc and the storage class used is fast001.

Congratulations, you have successfully installed StorageOS on Kubernetes, created a volume, and bound that volume to an application!

cd <directory>	Change directory
ls	List directory
echo 'contents' > <file>	Write contents to a file
cat <file>	Output contents of file

i	In Command Mode	Change into Insert Mode, you can now insert and edit text in the file
esc	In Insert Mode	Change into Command Mode, you can now execute commands
:wq	In Command Mode	Save and Exit

Welcome!

StorageOS and Kubernetes

Congratulations!

You've completed the scenario!

Scenario Rating

Steps