Skip to content
This repository has been archived by the owner on Jun 21, 2022. It is now read-only.

Releases: mhausenblas/reshifter

Bug fix release

18 Jul 08:42
Compare
Choose a tag to compare
Bug fix release Pre-release
Pre-release

Attempts to fix #2

Bug fixes and elapsed time of restore

17 Jul 05:11
Compare
Choose a tag to compare
Pre-release

This release contains all the 0.3.10 features and fixes some bugs. Also, adds support for elapsed time of a restore.

Fixes #2

15 Jul 18:05
Compare
Choose a tag to compare
Fixes #2 Pre-release
Pre-release

A bug fix release, addressing #2 (background: legacy key space in a v3 etcd).

Now with backup file upload

12 Jul 09:02
Compare
Choose a tag to compare
Pre-release

All of the 0.3.8 functionality and now you can also upload backup files when restoring the cluster, both in HTTP API and app/UI (restore tab).

Support for legacy key spaces

09 Jul 08:21
Compare
Choose a tag to compare
Pre-release

In previous versions of Kubernetes, the key space used by etcd was /registry, see also the docs here. With this version of ReShifter, these legacy key spaces are now also recognized and supported in discovery and backup packages.

Adds listing backups from remote S3

07 Jul 14:45
Compare
Choose a tag to compare
Pre-release

All the 0.3.6 sweetness and now you can also list available backups from a remote S3-compatible storage.

Usage from the HTTP API:

$ curl "http://localhost:8080/v1/backup/all?remote=play.minio.io:9000&bucket=reshifter-2017-06-30"

Usage from CLI:

$ rcli backup list -r play.minio.io:9000 -b reshifter-2017-06-30

If you don't provide the remote/bucket parameters, ReShifter defaults to what it did so far: it lists the backup IDs available in the (local) work directory.

Initial supports for different backup strategies

07 Jul 10:40
Compare
Choose a tag to compare

All of the 0.3.5 functionality and now you can, by specifying the RS_BACKUP_STRATEGY environment variable, influence how ReShifter does the backup. Currently two strategies are supported:

  • RS_BACKUP_STRATEGY=raw is the default and does exactly what ReShifter did so far, that is, storing the content of well-known keys to disk
  • RS_BACKUP_STRATEGY=render is a strategy that prints the content on the screen, useful for debugging, mainly for the CLI. For example, to dump the relevant content of etcd to screen you can use RS_BACKUP_STRATEGY=render rcli backup create.

Adds listing backups to HTTP API and CLI

06 Jul 09:13
Compare
Choose a tag to compare

All the functionality of v0.3.4 and now you can get a list of all (local) backups in the HTTP API via the /v1/backup/all endpoint as well as via rcli backup list.

Endpoint stats everywhere

01 Jul 11:00
Compare
Choose a tag to compare
Pre-release

This release adds the endpoint stats to the CLI tool, so now you can benefit from this feature from both the HTTP API as well as from the CLI.

The stats release

01 Jul 06:39
Compare
Choose a tag to compare
The stats release Pre-release
Pre-release

This release adds endpoint statistics. That is, in the API you can now get the number of keys and the overall volume of data to be backed up in bytes via the /v1/epstats/ endpoint, before you do a backup. The response is something like:

{
  "numkeys": 100,
  "totalsizevalbytes": 359884
}