Understanding Satellite storage
Before you can decide what type of storage is correct for your Satellite clusters, you must understand the infrastructure provider, your app requirements, the type of data that you want to store, and how often you want to access this data. For more information, see choosing a storage solution.
Before you can use storage templates and configurations to manage your storage resources across locations and clusters, make sure you Set up Satellite Config in your location.
What are Satellite storage templates?
Satellite storage templates are the framework for a storage configuration. When you use a Satellite storage template to create a configuration, you include the details for your selected storage provider. Each template contains a set of parameters that is specific to the storage provider. These parameters include user credentials, device information, worker nodes, and more. After you use a template to create a storage configuration, you can reuse that configuration to assign storage across your Satellite clusters. Each template is will receive revision and version updates.
- Storage template
- Satellite storage templates are preset storage formats that enable you to create storage configurations that can be applied across clusters without the need to re-create the configuration for each cluster.
- Storage configuration
- A storage configuration contains the necessary information to provision your storage resources in your cluster.
- Storage assignment
- A storage assignment is a storage configuration applied to your cluster.
- Revision
- A revision update resolves breaking issues and includes security patches. For example, updating from version
1.5
to1.6
. - Version
- A major update to the template version. For example, updating from version
1.0
to2.0
. Version updates can add new template parameters, change storage resources, and are more disruptive than revision updates.
What are my options for deploying storage to Satellite?
You have two options when configuring storage in Satellite. The first is by using one of the provided storage templates. The second is by bringing your own storage drivers (BYOD), Helm charts, or Operators from the IBM Cloud Catalog, OperatorHub, or GitHub repo.
- Satellite storage templates
- You can create storage configurations by using the Satellite storage template for the storage provider or driver that you want to use. After you create a storage configuration by using a template, you can assign your storage configuration to your clusters or services. By using storage templates, you can create storage configurations that can be consistently assigned, updated, and managed across the clusters, service clusters, and cluster groups in your location.
- Bring your own Operators, drivers, and plug-ins
- You can also bring your own storage drivers to Satellite by installing them from the Catalog, OperatorHub, Helm charts, or by using your preferred method of deploying images to your clusters including images and drivers from various IBM Cloud storage and partner solutions, for example Portworx. Bringing your own storage driver is functionally supported, but you are responsible for the entire lifecycle operations, installation, troubleshooting, and support.
While bringing your own drivers or operators to your Satellite clusters is possible, if you want to deploy IBM Cloud services that use storage make sure you use one of the provided storage templates.
Which deployment option should I use?
Since Satellite storage templates are supported by IBM Cloud and the configurations that you create by deploying templates can be used across your Satellite clusters, service clusters, and cluster groups, templates are the preferred option when setting up storage for services in Satellite.
If the storage solution that you want to use does not have a Satellite template available, check the IBM Cloud Catalog for supported Helm charts and Operators.
What are the benefits of using templates?
With Satellite storage templates, you can create a storage configuration that can be deployed across your clusters without the need to re-create the configuration for each cluster.
The Satellite storage templates are provided and tested by IBM or third-party vendors. IBM provides the configuration tooling to install the storage drivers on clusters in your Satellite location as described in the templates. For issues with the installation process, you can contact IBM. However, for issues with lifecycle operations of the storage devices, contact the storage provider.
When you use a Satellite storage template to create a configuration, you include the details for the storage provider that you want to use. Each template contains a set of parameters that is specific to the storage provider. These parameters include things like credentials, device information, worker nodes, and more. After you use a template to create a storage configuration, you can reuse that configuration to assign storage across your Satellite clusters.
You can also quickly update the configuration parameters and apply them automatically across clusters, service clusters, and cluster groups in your locations.
Feature or benefit | Satellite storage templates | Bring your own drivers |
---|---|---|
Integrated with the Satellite interface. | Yes | No |
Quickly and consistently install storage drivers across multiple clusters. | Yes | No |
Repeatable, site-specific or storage-specific configurations. | Yes | No |
Certified and tested with Satellite. | Yes | No |
How do templates work?
When you create a configuration by using a template, you specify a set of parameters for the storage provider that you want to use. These parameters preset values that are used when you deploy storage drivers, create persistent volumes, provision instances, or use other functions depending on the provider and the type of storage that you want to use. For more information, see the list of available storage templates.
The following image depicts the workflow for creating a Satellite storage configuration by using a storage template.
- Select the storage template that you want to use for your configuration.
- Create a Satellite cluster. Make sure that you select the Enable cluster admin access for Satellite Config option when you create the cluster. If you don't enable Administrator (admin) access for Satellite Config when creating your cluster, you must re-create your cluster and enable admin access before you can deploy storage.
- Assign your Satellite storage configuration to your clusters.
- Satellite deploys the storage drivers and any solution-specific resources for the provider that you selected to the clusters that you assigned the storage configuration to.
How do I manage updates?
Satellite storage template updates include major version updates or patch updates, also called revisions.
- Version
- A major update to the template version. For example, updating from version
1.0
to2.0
. Version updates can add new template parameters, change storage resources, and are more disruptive than revision updates. Version updates may require you to reload or attach new hosts, redeploy services, - Patch (Revision)
- Patch updates, also called revisions, contain bug fixes and security vulnerability patches. You can apply patches manually to each of your storage configurations and assignments or you enable automatic patch updates to ensure you get the latest
bug fixes and security updates. For more information about enabling automatic patches, see the
ibmcloud sat storage assignment autopatch
command reference.
Which storage templates are available?
You can create a Satellite storage configuration by using a template for the storage provider that you want to use. If your preferred storage provider does not have a template, you can create your own configuration template or you can manually deploy storage drivers. The following list includes the storage templates are currently available to deploy to your Satellite clusters.
Template name | Template CLI name | Version, Patch | Supported status | Change log |
---|---|---|---|---|
AWS EBS CSI Driver | aws-ebs-csi-driver |
Version: 1.1.0, Patch: 5 | Deprecated | Change log |
AWS EBS CSI Driver | aws-ebs-csi-driver |
Version: 1.5.1, Patch: 5 | Deprecated | Change log |
AWS EBS CSI Driver | aws-ebs-csi-driver |
Version: 1.12.0 (Default), Patch: 3 | Supported | Change log |
AWS EBS CSI Driver | aws-ebs-csi-driver |
Version: 1.31.0, Patch: 1 | Supported | Change log |
AWS EFS CSI Driver | aws-efs-csi-driver |
Version: 1.3.1, Patch: 4 | Deprecated | Change log |
AWS EFS CSI Driver | aws-efs-csi-driver |
Version: 1.3.7, Patch: 4 | Deprecated | Change log |
AWS EFS CSI Driver | aws-efs-csi-driver |
Version: 1.4.2 (Default), Patch: 1 | Supported | Change log |
AWS EFS CSI Driver | aws-efs-csi-driver |
Version: 2.0.3, Patch: 1 | Supported | Change log |
Azure Disk CSI Driver | azuredisk-csi-driver |
Version: 1.4.0, Patch: 5 | Supported | Change log |
Azure Disk CSI Driver | azuredisk-csi-driver |
Version: 1.18.0, Patch: 5 | Supported | Change log |
Azure Disk CSI Driver | azuredisk-csi-driver |
Version: 1.23.0 (Default), Patch: 1 | Supported | Change log |
Azure File CSI Driver | azurefile-csi-driver |
Version: 1.9.0, Patch: 4 | Supported | Change log |
Azure File CSI Driver | azurefile-csi-driver |
Version: 1.18.0, Patch: 4 | Supported | Change log |
Azure File CSI Driver | azurefile-csi-driver |
Version: 1.22.0 (Default), Patch: 1 | Supported | Change log |
GCP Compute Persistent Disk CSI Driver | gcp-compute-persistent-disk-csi-driver |
Version: 1.0.4, Patch: 4 | Deprecated | Change log |
GCP Compute Persistent Disk CSI Driver | gcp-compute-persistent-disk-csi-driver |
Version: 1.7.1, Patch: 5 | Supported | Change log |
GCP Compute Persistent Disk CSI Driver | gcp-compute-persistent-disk-csi-driver |
Version: 1.8.0 (Default), Patch: 2 | Supported | Change log |
IBM Object Storage Plugin | ibm-object-storage-plugin |
Version: 2.2 (Default), Patch: 23 | Supported | Change log |
IBM System Storage Block CSI driver | ibm-system-storage-block-csi-driver |
Version: 1.10.0, Patch: 1 | Deprecated | Change log |
IBM System Storage Block CSI driver | ibm-system-storage-block-csi-driver |
Version: 1.11.1 (Default), Patch: 1 | Supported | Change log |
IBM System Storage Block CSI driver | ibm-system-storage-block-csi-driver |
Version: 1.11.2, Patch: 1 | Supported | Change log |
[Beta] IBM VPC Block CSI driver | ibm-vpc-block-csi-driver |
Version: 5.1 (Default), Patch: 7 | Supported | Change log |
[Beta] Local Storage File and/or Block | local-storage |
Version: 1.0.0 (Default), Patch: 1 | Supported | Change log |
Local Storage Operator | local-storage-operator |
Version: 1.0.0 (Default), Patch: 1 | Supported | Change log |
Local Storage Operator - Block | local-volume-block |
Version: 4.9, Patch: 4 | Deprecated | Change log |
Local Storage Operator - Block | local-volume-block |
Version: 4.10, Patch: 4 | Supported | Change log |
Local Storage Operator - Block | local-volume-block |
Version: 4.11, Patch: 1 | Supported | Change log |
Local Storage Operator - Block | local-volume-block |
Version: 4.12, Patch: 1 | Supported | Change log |
Local Storage Operator - Block | local-volume-block |
Version: 4.13 (Default), Patch: 1 | Supported | Change log |
Local Storage Operator - File | local-volume-file |
Version: 4.9, Patch: 4 | Deprecated | Change log |
Local Storage Operator - File | local-volume-file |
Version: 4.10, Patch: 4 | Supported | Change log |
Local Storage Operator - File | local-volume-file |
Version: 4.11, Patch: 1 | Supported | Change log |
Local Storage Operator - File | local-volume-file |
Version: 4.12, Patch: 1 | Supported | Change log |
Local Storage Operator - File | local-volume-file |
Version: 4.13 (Default), Patch: 1 | Supported | Change log |
NetApp Ontap-NAS Driver | netapp-ontap-nas |
Version: 22.04, Patch: 26 | Supported | Change log |
NetApp Ontap-NAS Driver | netapp-ontap-nas |
Version: 22.10, Patch: 13 | Supported | Change log |
NetApp Ontap-NAS Driver | netapp-ontap-nas |
Version: 24.02 (Default), Patch: 2 | Supported | Change log |
NetApp Ontap-SAN Driver | netapp-ontap-san |
Version: 22.04, Patch: 26 | Supported | Change log |
NetApp Ontap-SAN Driver | netapp-ontap-san |
Version: 22.10, Patch: 13 | Supported | Change log |
NetApp Ontap-SAN Driver | netapp-ontap-san |
Version: 24.02 (Default), Patch: 2 | Supported | Change log |
NetApp Trident Operator | netapp-trident |
Version: 22.04, Patch: 3 | Supported | Change log |
NetApp Trident Operator | netapp-trident |
Version: 22.10, Patch: 1 | Supported | Change log |
NetApp Trident Operator | netapp-trident |
Version: 24.02 (Default), Patch: 1 | Supported | Change log |
OpenShift Data Foundation for local devices | odf-local |
Version: 4.12, Patch: 15 | Supported | Change log |
OpenShift Data Foundation for local devices | odf-local |
Version: 4.13, Patch: 12 | Supported | Change log |
OpenShift Data Foundation for local devices | odf-local |
Version: 4.14, Patch: 8 | Supported | Change log |
OpenShift Data Foundation for local devices | odf-local |
Version: 4.15 (Default), Patch: 5 | Supported | Change log |
OpenShift Data Foundation for remote storage | odf-remote |
Version: 4.12, Patch: 15 | Supported | Change log |
OpenShift Data Foundation for remote storage | odf-remote |
Version: 4.13, Patch: 12 | Supported | Change log |
OpenShift Data Foundation for remote storage | odf-remote |
Version: 4.14, Patch: 8 | Supported | Change log |
OpenShift Data Foundation for remote storage | odf-remote |
Version: 4.15 (Default), Patch: 5 | Supported | Change log |
VMware CSI Driver | vsphere-csi-driver |
Version: 2.5.1, Patch: 6 | Supported | Change log |
VMware CSI Driver | vsphere-csi-driver |
Version: 2.7.0 (Default), Patch: 3 | Supported | Change log |