Rancher Catalog Install

StorageOS is a Certified application in the Rancher Catalog. You can install StorageOS using the Rancher application install.

1. Select the System project of your cluster

   

2. Select the Apps tab and click Launch

3. Search for StorageOS and click on the App

4. Define the StorageOS cluster installation

   A generic configuration for StorageOS is preset using the default values in the form. The values in the form can be changed to customize the installation. To customize the installation further, set Install StorageOS Cluster to false and use a yaml definition for the StorageOSCluster Custom Resource.

    

   The following options are exposed by the form to allow some simple customization of the StorageOS installation.

   • Cluster Operator namespace : The Kubernetes namespace where the StorageOS Cluster Operator controller and other resources will be created.
   • Container Images : By default images are pulled from DockerHub, you can specify the image URLs when using private registries.
   • Conditional bootstrap of StorageOS : Controls the automatic deployment of StorageOS after installing the Cluster Operator. If set to false, the Operator will be created, but the Custom Resource will not be applied to the cluster. Launch the operator and proceed to the section Custom Resource definition. For more information check the Operator documentation and CR examples.
   • StorageOS namespace : The Kubernetes namespace where StorageOS will be installed. Installing into the kube-system namespace will add StorageOS to a priority class to ensure high priority resource allocation. Installing StorageOS with the priority class prevents StorageOS from being evicted during periods of resource contention.
   • Username/Password : Default Username and Password for the admin account to be created at StorageOS bootstrap. A random password will be generated by leaving the field empty or clicking the Generate button.
   • Key-value store setup : Connection and configuration details for an external Etcd cluster. StorageOS can use an external key-value store to hold configuration. Settings such as external etcd with TLS termination are available.
   • Node Selectors and Tolerations : Control placement of StorageOS DaemonSet Pods. StorageOS will only be installed on the selected nodes. Can be used in conjunction with tolerations.

    

   

5. Verify the cluster bootstrap has successfully completed

   

Custom Resource definition

If Install StorageOS Cluster was set to false, StorageOS will not be bootstrapped automatically. After the StorageOS Operator is installed, you can now create a Custom Resource that describes the StorageOS cluster.

1. Select the System Workloads and Import YAML

2. Create the Secret and CustomResource

   This is an example.

   apiVersion: v1
   kind: Secret
   metadata:
     name: "storageos-api"
     namespace: "storageos-operator"
     labels:
       app: "storageos"
   type: "kubernetes.io/storageos"
   data:
     # echo -n '<secret>' | base64
     apiUsername: c3RvcmFnZW9z # Define your own user and password
     apiPassword: c3RvcmFnZW9z
   ---
   apiVersion: "storageos.com/v1"
   kind: StorageOSCluster
   metadata:
     name: "storageos"
   spec:
     k8sDistro: "rancher"
     namespace: "kube-system"
     secretRefName: "storageos-api" # Reference from the Secret created in the previous step
     secretRefNamespace: "storageos-operator"  # Namespace of the Secret
     csi:
       enable: true
       deploymentStrategy: "deployment"
     images:
       nodeContainer: "storageos/node:{{ site.latest_node_version }}" # StorageOS version
   #  kvBackend:
   #    address: 'storageos-etcd-client.etcd:2379' # Example address, change for your etcd endpoint
   #    backend: 'etcd'
     sharedDir: '/var/lib/kubelet/plugins/kubernetes.io~storageos' # Needed when Kubelet runs as a container
     resources:
       requests:
         memory: "512Mi"
     nodeSelectorTerms:
       - matchExpressions:
         - key: "node-role.kubernetes.io/worker"
           operator: In
           values:
           - "true"
   

   Additional spec parameters are available on the [Cluster Operator configuration]({%link _docs/reference/cluster-operator/configuration.md %}) page.

   You can find more examples such as deployments referencing a external etcd kv store for StorageOS in the Cluster Operator examples page.