Understanding Stork in Portworx Backup
Stork is a cloud native storage operator runtime scheduler plugin. It translates decisions of a scheduler orchestration system in such a way that an external cloud native storage solution can act upon. By doing so, Stork extends Kubernetes capabilities with the help of the underlying storage provider, making it more stateful aware.
Stork facilitates stateful workflows such as snapshots, clones, cloud backups, and migrations. Stork provides:
- Kubernetes native mechanism for executing these workflows, and makes it aware of storage and scheduler.
- A storage provider-agnostic method for executing these workflows.
Where is Stork installed?
Stork is an agent that needs to be installed on all clusters where you want to back up from and restore to. Stork bridges the gap between Portworx Backup running on your administration cluster, and the remaining clusters, where you need to back up from and restore to.
Stork acts as an abstraction layer between the underlying storage provider and Portworx Backup. Stork enables Portworx Backup to perform the following tasks:
- Execute backups and restores on the target cluster
- Push the Kubernetes resources to the configured object storage location
- Integrate with storage providers for taking snapshots and pushing snapshots to object storage
Prepare air-gapped environment
If your application cluster is air-gapped, then you must pull the following
openstorage images before installing Portworx Backup:
You must then push the above images to your internal registry server, accessible by the air-gapped nodes.
After pushing the images, follow the instructions in the Install Portworx Backup on-premises section to install Portworx Backup.