e13806e0b8
Some aws implementations, for example the quobyte object storage, do not
support the v4 signing algorithm, but only v1.
This makes it possible to configure the signatureVersion.
The algorithm implementation was ported from d6c1be296e/botocore/auth.py (L860-L862)
which is used by the aws CLI client.
This fixes https://github.com/heptio/ark/issues/811.
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
2.6 KiB
Compatible Storage Providers
Ark supports a variety of storage providers for different backup and snapshot operations. As of version 0.6.0, a plugin system allows anyone to add compatibility for additional backup and volume storage platforms without modifying the Ark codebase.
Backup Storage Providers
| Provider | Owner | Contact |
|---|---|---|
| AWS S3 | Ark Team | Slack, GitHub Issue |
| Azure Blob Storage | Ark Team | Slack, GitHub Issue |
| Google Cloud Storage | Ark Team | Slack, GitHub Issue |
S3-Compatible Backup Storage Providers
Ark uses Amazon's Go SDK to connect to the S3 API. Some third-party storage providers also support the S3 API, and users have reported the following providers work with Ark:
Note that these providers are not regularly tested by the Ark team.
- IBM Cloud
- Minio
- Ceph RADOS v12.2.7
- DigitalOcean
- Quobyte
Some storage providers, like Quobyte, may need a different signature algorithm version.
Volume Snapshot Providers
| Provider | Owner | Contact |
|---|---|---|
| AWS EBS | Ark Team | Slack, GitHub Issue |
| Azure Managed Disks | Ark Team | Slack, GitHub Issue |
| Google Compute Engine Disks | Ark Team | Slack, GitHub Issue |
| Restic | Ark Team | Slack, GitHub Issue |
| Portworx | Portworx | Slack, GitHub Issue |
| DigitalOcean | StackPointCloud |
Adding a new plugin
To write a plugin for a new backup or volume storage system, take a look at the example repo.
After you publish your plugin, open a PR that adds your plugin to the appropriate list.