Stash v0.9.0-rc.2 comes with some bug fixes and improvements since v0.9.0-rc.1 release. Please, try it and give us your valuable feedback. To install, please follow the guide here.
Retention Policy for VolumeSnapshot: We have implemented retention policy for VolumeSnapshot. Now, your old VolumeSnapshots will be automatically garbage collected according to retention policy. Ref: stashed/stash#926.
Fix Argument Passing: We have fixed argument passing to database backup/restore commands. Ref: stashed/mongodb#5, stashed/postgres#17, stashed/elasticsearch#8, stashed/mysql#9.
BackupSession API Revision: Now a BackupSession can be triggered via spec.invoker instead of spec.backupConfiguration field. This breaking api change is done in preparation for upcoming BackupBatch crd support. Ref: stashed/stash#890, stashed/stash#931, stashed/docs#44.
spec.invoker instead of spec.backupConfiguration in BackupSession stashed/docs#44--enable-status-subresource flag stashed/postgres#18--enable-status-subresource flag stashed/mongodb#7--enable-status-subresource flag stashed/mysql#10Stash v0.9.0-rc.1 comes with documentation and respective charts for addons to backup databases. It also comes with some bug fixes since v0.9.0-rc.0 release. We have also introduced a kubectl plugin for Stash in this release. Please, try it and give us your valuable feedback. To install, please follow the guide here.
Addon Support: Stash addons enable users to extend it’s functionality to backup/restore any type of custom workloads. This release includes respective documentations and charts for PostgreSQL, MySQL, MongoDB, and Elasticsearch databases. This enables Stash to backup various KubeDB supported databases. You can also write your own addon to backup your custom target. We will include a guide on how to build addon for Stash in a future release.
Stash kubectl Plugin (Alpha): We have introduced an experimental Stash kubectl plugin. This will help you to unlock repository, trigger instant backup and copy various Stash resources between namespace and more.
Introduce BackupHistoryLimit: Now, you can configure how many BackupSession and associate resources (Job, PVC etc) to keep for each backup target. By default, Stash will keep only the history of last backup for debugging purpose. You can configure it using spec.backupHistoryLimit field of BackupConfiguration.
Introduce InterimVolumeTemplate: We have introduced a new field called InterimVolumeTemplate that can be used to pass a PVC template for storing temporary backup/restore data before uploading to backup or injecting into target. For more details, please visit here.
Allow subPath in Auto-Backup Annotation: Now, you can provide subPath in auto-backup annotation. For more details, please check here.
Use Kubebuilder to Generate CRDs: We have moved to kubernetes-sigs/kubebuilder for generating CRDs for Stash.
andionice` is missing in distroless image #882NICE and IONICE into distroless image #883We are very excited to announce Stash v0.9.0-rc.0. This release introduces v1beta1 API and a design overhaul. The new API and design enable Stash to support the use cases that were not possible before. This makes Stash more powerful, transparent, extensible and customizable. We are expecting that this new API will graduate to GA after some maturity. Check out the new architecture from here.
This release introduces lots of new features and changes. A summary of these new features is given below:
The following custom resources have been introduced in this release:
In addition to improving existing features, this release introduces the following new features:
Backup & Restore Stand-alone PVC : Stash now supports taking backup of a stand-alone PVC. To learn more about how Stash takes backup of a stand-alone PVC, please visit here.
Backup & Restore Databases : Stash now can backup PostgreSQL, MongoDB, Elasticsearch and MySQL databases in both stand-alone and clustered mode. To learn more about how Stash takes backup of a database, please visit here.
VolumeSnapshot : Now, you can take a scheduled snapshot of the volumes of a workload using Kubernetes VolumeSnapshot API. Check out how volume snapshotting works in Stash from here.
Instant Backup : You can now trigger a backup instantly. To learn how, please visit here.
Auto Backup : Now, Stash will let you configure a common template to backup similar types of target. You will require to add just a few annotations to the targeted workload to enable backup for it. Want to know how? Please visit here.
Support PSP Enabled Cluster : Stash now supports PSP enabled cluster.
Improved Prometheus Metrics : We have improved Prometheus metrics in this release. Check out the new metrics from here.
Support REST Server as Backend : Stash now supports REST server as backend. To learn how to configure REST backend, please visit here.
KubeDB Integration : Stash now seemingly integrates with KubeDB. It is now recommended tool to backup & restore KubeDB supported databases.
For a complete feature list of this release, please visit here.
appscode/stash repository into multiple repositories (stashed/stash, stashed/installer, stashed/docs). This enables us to push emergency fixes to installer and docs without requiring to cut a new release.Makefile based build process. This makes building Stash from source code simple and easy (#800).0.8.3 to 0.9.5 (#789).v1.14.0 (#775).failurePolicy: Ignore in webhooks for Kubernetes official resources. So, Stash will no longer cause any problem for creating new Kubernetes resources when it is not ready (#726).--rbac flag. Now, Stash will always start in RBAC enabled mode (#761).stash.appscode.dev/stash (#776).If you are upgrading Stash from 0.8.3 to this version, pay attention to the following things:
What will work: - Exiting scheduled backup will continue to work. - Scheduling new backup using Restic crd will work. - Restoring the already backed up data using Recovery crd will work.
What will not work:
- Restoring the data that was backed up using old API (Restic) with the new API (RestoreSession) will not work.
- Restoring the data that was backed up using new API (BackupConfiguration) with the old API (Recovery) will not work.
- Using new API (BackupConfiguration ) to backup into already existing Repository will not work. Stash will upload all targeted data again into the backend. Old snapshots will not be usable any more.
- Old Grafana dashboard will not work with new metrics.
--rbac flag #705nice and ionice for backup command #366bs short name for BackupSession #859 (tamalsaha)make container #818 (tamalsaha)