v0.11.0

Highlights

• Heptio Ark is now Velero! This release is the first one to use the new name. For details on the changes and how to migrate to v0.11, see the migration instructions. Please follow the instructions to ensure a successful upgrade to v0.11.
• Restic has been upgraded to v0.9.4, which brings significantly faster restores thanks to a new multi-threaded restorer.
• Velero now waits for terminating namespaces and persistent volumes to delete before attempting to restore them, rather than trying and failing to restore them while they're being deleted.

All Changes

• Fix concurrency bug in code ensuring restic repository exists (#1235, @skriss)
• Wait for PVs and namespaces to delete before attempting to restore them. (#826, @nrb)
• Set the zones for GCP regional disks on restore. This requires the compute.zones.get permission on the GCP serviceaccount in order to work correctly. (#1200, @nrb)
• Renamed Heptio Ark to Velero. Changed internal imports, environment variables, and binary name. (#1184, @nrb)
• use 'restic stats' instead of 'restic check' to determine if repo exists (#1171, @skriss)
• upgrade restic to v0.9.4 & replace --hostname flag with --host (#1156, @skriss)
• Clarify restore log when object unchanged (#1153, @daved)
• Add backup-version file in backup tarball. (#1117, @wwitzel3)
• add ServerStatusRequest CRD and show server version in ark version output (#1116, @skriss)

v0.10.2

Changes

• upgrade restic to v0.9.4 & replace --hostname flag with --host (#1156, @skriss)
• use 'restic stats' instead of 'restic check' to determine if repo exists (#1171, @skriss)
• Fix concurrency bug in code ensuring restic repository exists (#1235, @skriss)

v0.10.1

Changes

• Fix minio setup job command (#1118, @acbramley)
• Add debugging-install link in doc get-started.md (#1131, @hex108)
• ark version: show full git SHA & combine git tree state indicator with git SHA line (#1124, @skriss)
• Delete spec.priority in pod restore action (#879, @mwieczorek)
• Allow to use AWS Signature v1 for creating signed AWS urls (#811, @bashofmann)
• add multizone/regional support to gcp (#765, @wwitzel3)
• Fixed the newline output when deleting a schedule. (#1120, @jwhitcraft)
• Remove obsolete make targets and rename 'make goreleaser' to 'make release' (#1114, @skriss)
• Update to go 1.11 (#1069, @gliptak)
• Update CHANGELOGs (#1063, @wwitzel3)
• Initialize empty schedule metrics on server init (#1054, @cbeneke)
• Added brew reference (#1051, @omerlh)
• Remove default token from all service accounts (#1048, @ncdc)
• Add pprof support to the Ark server (#234, @ncdc)

v0.10.0

Highlights

• We've introduced two new custom resource definitions, BackupStorageLocation and VolumeSnapshotLocation, that replace the Config CRD from previous versions. As part of this, you may now configure more than one possible location for where backups and snapshots are stored, and when you create a Backup you can select the location where you'd like that particular backup to be stored. See the [Locations documentation][2] for an overview of this feature.
• Ark's plugin system has been significantly refactored to improve robustness and ease of development. Plugin processes are now automatically restarted if they unexpectedly terminate. Additionally, plugin binaries can now contain more than one plugin implementation (e.g. and object store and a block store, or many backup item actions).
• The sync process, which ensures that Backup custom resources exist for each backup in object storage, has been revamped to run much more frequently (once per minute rather than once per hour), to use significantly fewer cloud provider API calls, and to not generate spurious Kubernetes API errors.
• Ark can now be configured to store all data under a prefix within an object storage bucket. This means that you no longer need a separate bucket per Ark instance; you can now have all of your clusters' Ark backups go into a single bucket, with each cluster having its own prefix/subdirectory within that bucket.
• Restic backup data is now automatically stored within the same bucket/prefix as the rest of the Ark data. A separate bucket is no longer required (or allowed).
• Ark resources (backups, restores, schedules) can now be bulk-deleted through the ark CLI, using the --all or --selector flags, or by specifying multiple resource names as arguments to the delete commands.
• The ark CLI now supports waiting for backups and restores to complete with the --wait flag for ark backup create and ark restore create
• Restores can be created directly from the most recent backup for a schedule, using ark restore create --from-schedule SCHEDULE_NAME

Breaking Changes

Heptio Ark v0.10 contains a number of breaking changes. Upgrading will require some additional steps beyond just updating your client binary and your container image tag. We've provided a [detailed set of instructions][1] to help you with the upgrade process. Please read and follow these instructions
carefully to ensure a successful upgrade!

• The Config CRD has been replaced by BackupStorageLocation and VolumeSnapshotLocation CRDs.
• The interface for external plugins (object/block stores, backup/restore item actions) has changed. If you have authored any custom plugins, they'll need to be updated for v0.10.
  • The ObjectStore.ListCommonPrefixes signature has changed to add a prefix parameter.
  • Registering plugins has changed. Create a new plugin server with the NewServer function, and register plugins with the appropriate functions. See the Server interface for details.
• The organization of Ark data in object storage has changed. Existing data will need to be moved around to conform to the new layout.

All Changes

• b9de44ff update docs to reference config/ dir within release tarballs
• eace0255 goreleaser: update example image tags to match version being released
• cff02159 add rbac content, rework get-started for NodePort and publicUrl, add versioning information
• fa14255e add content for docs issue 819
• 22959071 add doc explaining locations
• e5556fe6 Added qps and burst to server's client
• 9ae861c9 Support a separate URL base for pre-signed URLs
• 698420b6 Update storage-layout-reorg-v0.10.md
• 6c9e1f18 lower some noisy logs to debug level
• 318fd8a8 add troubleshooting for loadbalancer restores
• defb8aa8 remove code that checks directly for a backup from restore controller
• 7abe1156 Move clearing up of metadata before plugin's actions
• ec013e6f Document upgrading plugins in the deployment
• d6162e94 fix goreleaser bugs
• a15df276 Add correct link and change role
• 46bed015 add 0.10 breaking changes warning to readme in master
• e3a7d6a2 add content for issue 994
• 400911e9 address docs issue #978
• b818cc27 don't require a default provider VSL if there's only 1
• 90638086 v0.10 changelog
• 6e2166c4 add docs page on versions and upgrading
• 18b434cb goreleaser scripts for building/creating a release on a workstation
• bb65d67a update restic prerequisite with min k8s version
• b5a2ccd5 Silence git detached HEAD advice in build container
• 67749141 instructions for upgrading to v0.10
• 516422c2 sync controller: fill in missing .spec.storageLocation
• 195e6aaf fix bug preventing PV snapshots from v0.10 backups from restoring
• bca58516 Run 'make update' to update formatting
• 573ce7d0 Update formatting script
• 90d9be59 support restoring/deleting legacy backups with .status.volumeBackups
• ef194972 rename variables #967
• 6d4e702c fix broken link
• 596eea1b restore storageclasses before pvs and pvcs
• f014cab1 backup describer: show snapshot summary by default, details optionally
• 8acc66d0 remove pvProviderExists param from NewRestoreController
• 57ce590f create a struct for multiple return of same type in restore_contoroller #967
• 028fafb6 Corrected grammatical error
• db856aff Specify return arguments
• 9952dfb0 Address #424: Add CRDs to list of prioritized resources
• cf2c2714 fix bugs in GetBackupVolumeSnapshots and add test
• ec124673 remove all references to Config from docs/examples
• c36131a0 remove Config-related code
• 406b50a7 update restore process using snapshot locations
• 268080ad avoid panics if can't get block store during deletion
• 4a03370f update backup deletion controller for snapshot locations
• 38c72b8c include snapshot locations in created schedule's backup spec
• 0ec2de55 azure: update blockstore to allow storing snaps in different resource group
• 35bb533c close gzip writer before uploading volumesnapshots file
• da9ed38c store volume snapshot info as JSON in backup storage
• e24248e0 add --volume-snapshot-locations flag to ark backup create
• df07b7dc update backup code to work with volume snapshot locations
• 4af89fa8 add unit test for getDefaultVolumeSnapshotLocations
• 02f50b9c add default-volume-snapshot-locations to server cmd
• 1aa712d2 Default and validate VolumeSnapshotLocations
• bbf76985 add create CLI command for snapshot locations
• aeb221ea Add printer for snapshot locations
• ffc612ac Add volume snapshot CLI get command
• f20342aa Add VolumeLocation and Snapshot.
• 7172db8a upgrade to restic v0.9.3
• 99adc4fa Remove broken references to docs that are not existing
• 474efde6 Fixed relative link for im...

v0.9.11

Bug Fixes

• Fix bug preventing PV snapshots from being restored (#1040, @ncdc)

Binary Checksums

7968aadee87d660309cdc6bb1ddb54b590f0e142815d9634cf5d8ef5ec057cfe  ark-v0.9.11-darwin-amd64.tar.gz
1bc93d529f372de43caa58c0041b238b0d479c37bdcf221df59856fcf7262c46  ark-v0.9.11-linux-amd64.tar.gz
d2ec8c8e1a163eda95fd8ca3be2ffb9a37c95da0861718be1d0af4aba810ff11  ark-v0.9.11-linux-arm.tar.gz
34ccf042c416d86010a68a24deea57cf735e482ab137c40ff564d67ce05216c3  ark-v0.9.11-linux-arm64.tar.gz
39e11d6382df48d606a8ba37f0ff591b92e9dc1046ca2ab47eec336f3ff4f6f7  ark-v0.9.11-windows-amd64.tar.gz
0e310e02c17f89b89bd1add3be52dcc211b8545de19b985137bfa5438998476d  CHECKSUM

v0.9.10

Bug Fixes

• restore storageclasses before pvs and pvcs (#594, @shubheksha)
• AWS: Ensure that the order returned by ListObjects is consistent (#999, @bashofmann)
• Add CRDs to list of prioritized resources (#424, @domenicrosati)
• Verify PV doesn't exist before creating new volume (#609, @nrb)
• Update README.md - Grammar mistake corrected (#1018, @midhunbiju)

Binary Checksums

e7ccd2d0502f8099ca8bbdcd2e1762d970d261dce56d009866163924217a289c  ark-v0.9.10-darwin-amd64.tar.gz
c2b0ad0a2d22b3a647fdc44c2d4dcefaac29671ec6191405de6f0580f7134a4d  ark-v0.9.10-linux-amd64.tar.gz
f64240221bdb7d6a3847c7700037112e9b77dbe43a151196f656c002fc2bff22  ark-v0.9.10-linux-arm.tar.gz
bdbdaff5a96b075bfdd8a3b8abafbe1431e87ee9d7f61ed2fb2d238b25578532  ark-v0.9.10-linux-arm64.tar.gz
b1dce93e9081dd747db9bd1716ded6a693ec3ae1d051d0c86b584d50e1ee4085  ark-v0.9.10-windows-amd64.tar.gz
16d7a6d959bac917d3d73dc9beff0b5bb75ef6734022a5b445e278bbb5737781  CHECKSUM

v0.10.0-beta.1

Highlights

• We've introduced two new custom resource definitions, BackupStorageLocation and VolumeSnapshotLocation, that replace the Config CRD from
  previous versions. As part of this, you may now configure more than one possible location for where backups and snapshots are stored, and when you
  create a Backup you can select the location where you'd like that particular backup to be stored.
• Ark's plugin system has been significantly refactored to improve robustness and ease of development. Plugin processes are now automatically restarted
  if they unexpectedly terminate. Additionally, plugin binaries can now contain more than one plugin implementation (e.g. and object store and a block store,
  or many backup item actions).
• The sync process, which ensures that Backup custom resources exist for each backup in object storage, has been revamped to run much more frequently (once
  per minute rather than once per hour), to use significantly fewer cloud provider API calls, and to not generate spurious Kubernetes API errors.
• Ark can now be configured to store all data under a prefix within an object storage bucket. This means that you no longer need a separate bucket per Ark
  instance; you can now have all of your clusters' Ark backups go into a single bucket, with each cluster having its own prefix/subdirectory
  within that bucket.
• Restic backup data is now automatically stored within the same bucket/prefix as the rest of the Ark data. A separate bucket is no longer required (or allowed).
• Ark resources (backups, restores, schedules) can now be bulk-deleted through the ark CLI, using the --all or --selector flags, or by specifying
  multiple resource names as arguments to the delete commands.
• The ark CLI now supports waiting for backups and restores to complete with the --wait flag for ark backup create and ark restore create
• Restores can be created directly from the most recent backup for a schedule, using ark restore create --from-schedule SCHEDULE_NAME

Breaking Changes

Heptio Ark v0.10 contains a number of breaking changes. Upgrading will require some additional steps beyond just updating your client binary and your
container image tag. We've provided a [detailed set of instructions][1] to help you with the upgrade process. Please read and follow these instructions
carefully to ensure a successful upgrade!

• The Config CRD has been replaced by BackupStorageLocation and VolumeSnapshotLocation CRDs.
• The interface for external plugins (object/block stores, backup/restore item actions) has changed. If you have authored any custom plugins, they'll
  need to be updated for v0.10.
  • The ObjectStore.ListCommonPrefixes signature has changed to add a prefix parameter.
  • Registering plugins has changed. Create a new plugin server with the NewServer function, and register plugins with the appropriate functions. See the Server interface for details.
• The organization of Ark data in object storage has changed. Existing data will need to be moved around to conform to the new layout.

All Changes

• 195e6aaf fix bug preventing PV snapshots from v0.10 backups from restoring
• bca58516 Run 'make update' to update formatting
• 573ce7d0 Update formatting script
• 90d9be59 support restoring/deleting legacy backups with .status.volumeBackups
• ef194972 rename variables #967
• 6d4e702c fix broken link
• 596eea1b restore storageclasses before pvs and pvcs
• f014cab1 backup describer: show snapshot summary by default, details optionally
• 8acc66d0 remove pvProviderExists param from NewRestoreController
• 57ce590f create a struct for multiple return of same type in restore_contoroller #967
• 028fafb6 Corrected grammatical error
• db856aff Specify return arguments
• 9952dfb0 Address #424: Add CRDs to list of prioritized resources
• cf2c2714 fix bugs in GetBackupVolumeSnapshots and add test
• ec124673 remove all references to Config from docs/examples
• c36131a0 remove Config-related code
• 406b50a7 update restore process using snapshot locations
• 268080ad avoid panics if can't get block store during deletion
• 4a03370f update backup deletion controller for snapshot locations
• 38c72b8c include snapshot locations in created schedule's backup spec
• 0ec2de55 azure: update blockstore to allow storing snaps in different resource group
• 35bb533c close gzip writer before uploading volumesnapshots file
• da9ed38c store volume snapshot info as JSON in backup storage
• e24248e0 add --volume-snapshot-locations flag to ark backup create
• df07b7dc update backup code to work with volume snapshot locations
• 4af89fa8 add unit test for getDefaultVolumeSnapshotLocations
• 02f50b9c add default-volume-snapshot-locations to server cmd
• 1aa712d2 Default and validate VolumeSnapshotLocations
• bbf76985 add create CLI command for snapshot locations
• aeb221ea Add printer for snapshot locations
• ffc612ac Add volume snapshot CLI get command
• f20342aa Add VolumeLocation and Snapshot.
• 7172db8a upgrade to restic v0.9.3
• 99adc4fa Remove broken references to docs that are not existing
• 474efde6 Fixed relative link for image
• 41735154 don't require a default backup storage location to exist
• 0612c5de templatize error message in DeleteOptions
• 66bcbc05 add support for bulk deletion to ark schedule delete
• 3af43b49 add azure-specific code to support multi-location restic
• d009163b update restic to support multiple backup storage locations
• f4c99c77 Change link for the support matrix
• 91e45d56 Fix broken storage providers link
• ed0eb865 fix backup storage location example YAMLs
• eb709b8f only sync a backup location if it's changed since last sync
• af3af1b5 clarify Azure resource group usage in docs
• 9fdf8513 Minor code cleanup
• 2073e15a Fix formatting for live site
• 0fc3e8d8 add documentation on running Ark on-premises
• e46e89cb have restic share main Ark bucket
• 42b54586 refactor to make valid dirs part of an object store layout
• 8bc7e4f6 store backups & restores in backups/, restores/ subdirs in obj storage
• e3232b7e add support for bulk deletion to ark restore delete
• 17be71e1 remove deps used for docs gen
• 20635106 remove script for generating docs
• 6fd9ea9d remove cli reference docs and related scripts
• 4833607a Fix infinite sleep in fsfreeze container
• 7668bfd4 Add links for Portworx plugin support
• 468006e6 Fix Portworx name in doc
• e6b44539 Make fsfreeze image building consistent
• fcd27a13 get a new metadata accessor after calling backup item actions
• ffef86e3 Adding support for the AWS_CLUSTER_NAME env variable allowing to claim volumes ownership
• cda3dff8 Docum...

v0.9.9

Bug Fixes

• Check if initContainers key exists before attempting to remove volume mounts. (#927, @skriss)

Binary Checksums

1bfe0e4abea4d244cb927da44b569987ae34918a3bf67b6c609f630ef942bfc1  ark-v0.9.9-darwin-amd64.tar.gz
40709295202a36359549aa27a48c10a1bc4388ce0493891430b7cef6c6915a52  ark-v0.9.9-linux-amd64.tar.gz
2049f504a6e629dbee83fd109b382d937f6b138594fca38a6d455ab6bf530f80  ark-v0.9.9-linux-arm64.tar.gz
968e15c569589631fd74ca9e7e263d01917a61d84164a4f8275598dda98fd443  ark-v0.9.9-linux-arm.tar.gz
ff8051934520403ec9755c68a045ed62702dd5182ff286e4ce52930cf08c16ca  ark-v0.9.9-windows-amd64.tar.gz
ef1357987243b0c7c1095cef4c7493120ee020da4cc5daf7c96825a446b6d6cf  CHECKSUM

v0.9.8

Bug Fixes

• Discard service account token volume mounts from init containers on restore (#910, @james-powis)
• Support --include-cluster-resources flag when creating schedule (#942, @captjt)
• Remove logic to get a GCP project (#926, @shubheksha)
• Only try to back up PVCs linked PV if the PVC's phase is Bound (#920, @skriss)
• Claim ownership of new AWS volumes on Kubernetes cluster being restored into (#801, @ljakimczuk)
• Remove timeout check when taking snapshots (#928, @carlisia)

Binary Checksums

df173929a7b8874de112defcb6a07a3847c53f62594448df535f6d4c1f596ead  ark-v0.9.8-darwin-amd64.tar.gz
cc03f8f38a5fcb1097c6d2abd4f8041443ec8eab2ab5d72293f17dbe7b3a0993  ark-v0.9.8-linux-amd64.tar.gz
74c3a5c2862e15ac82ac0365ee20a4b731b4948151677f85533898c3f01da485  ark-v0.9.8-linux-arm64.tar.gz
7d782ee225b9a6dbbb79bfe979dbf9fa97a8af5ce2527cc6f153dc044886d396  ark-v0.9.8-linux-arm.tar.gz
368f3d1e5202361633046e2e16eba39d18f3bd45cf8debcaf79d3882097193d5  ark-v0.9.8-windows-amd64.tar.gz
33092a521b496fa35bdfe7bb8557cfef0ee8d47b2aef136a498744c393f4c77d  CHECKSUM

v0.9.8-beta.1

Bug Fixes

• Discard service account token volume mounts from init containers on restore (#910, @james-powis)

Binary Checksums

cd6eec8d7446ee174d01eec3502dc0c9ad4a637928b76cde1aacaf1e5b0e2ba9  ark-v0.9.8-beta.1-darwin-amd64.tar.gz
0f816d623652c09f5e044ada3ab4262add67af5d1a6b4df80ff4c21cbf8ca32e  ark-v0.9.8-beta.1-linux-amd64.tar.gz
93a0b7ee68f11260dcc623c236a79ebd53dcc25226f6f9ef646ec953a512743b  ark-v0.9.8-beta.1-linux-arm.tar.gz
c01e1847253158b32a9b436babb786c448633367e3c68d0a21cf20a90a2be76f  ark-v0.9.8-beta.1-linux-arm64.tar.gz
2496a7985205e180c65b2b6539da8a14e1b0b84a04cee768cc02652d22b586ab  ark-v0.9.8-beta.1-windows-amd64.tar.gz
6dca37afd1b6dbda5e1fed3dcb9de433495c1ab039e832d21740b6b695339935  CHECKSUM