Go to file
Adnan Abdulhussein 2156124dfc record PodVolumeBackup/Restore start and completion timestamps (#1609)
* record PodVolumeBackup start and completion timestamps

adds startTimestamp and completionTimestamp fields to the
PodVolumeBackup status spec

Signed-off-by: Adnan Abdulhussein <aadnan@vmware.com>

* record PodVolumeRestore start and completion timestamps

Signed-off-by: Adnan Abdulhussein <aadnan@vmware.com>
2019-06-28 11:58:02 -04:00
.github/ISSUE_TEMPLATE ark->velero in issue templates & bug cmd 2019-02-11 12:43:51 -07:00
changelogs record PodVolumeBackup/Restore start and completion timestamps (#1609) 2019-06-28 11:58:02 -04:00
cmd remove glog (#1559) 2019-06-10 15:44:44 -07:00
examples copy examples/ dir as-is to release tarballs 2019-04-25 13:09:58 -06:00
hack move issue-template-gen from docs/ to hack/ (#1558) 2019-06-10 15:22:27 -07:00
pkg record PodVolumeBackup/Restore start and completion timestamps (#1609) 2019-06-28 11:58:02 -04:00
site update README.md link to install docs, minor reorg install docs content 2019-06-25 09:00:40 -06:00
third_party/kubernetes/pkg/kubectl/cmd shortcut expander: use discovery helper's cached resource list 2019-05-07 12:23:45 -06:00
vendor remove glog (#1559) 2019-06-10 15:44:44 -07:00
.gitignore Docs updates - extra finishing touches (#1516) 2019-05-28 12:42:27 -04:00
.goreleaser.yml copy examples/ dir as-is to release tarballs 2019-04-25 13:09:58 -06:00
.travis.yml Only run CI when relevant files have changed 2019-05-30 17:32:23 -04:00
CHANGELOG.md add 1.0 changelog 2019-05-19 13:42:16 -06:00
CODE_OF_CONDUCT.md Rename Ark to Velero!!! 2019-02-04 17:35:22 -05:00
CONTRIBUTING.md remove all remaining legacy Ark references (#1415) 2019-04-29 12:33:54 -07:00
Dockerfile-fsfreeze-pause change base images to ubuntu:bionic 2019-05-15 12:56:20 -07:00
Dockerfile-velero change base images to ubuntu:bionic 2019-05-15 12:56:20 -07:00
Dockerfile-velero-restic-restore-helper change base images to ubuntu:bionic 2019-05-15 12:56:20 -07:00
Gopkg.lock remove glog (#1559) 2019-06-10 15:44:44 -07:00
Gopkg.toml remove glog (#1559) 2019-06-10 15:44:44 -07:00
LICENSE Initial commit 2017-08-02 13:27:17 -04:00
Makefile Add make serve-docs target for local viewing 2019-06-14 15:15:36 -04:00
README.md update README.md link to install docs, minor reorg install docs content 2019-06-25 09:00:40 -06:00
SUPPORT.md Update mailing list in SUPPORT.md 2019-04-23 20:45:56 -07:00
netlify.toml add velero.io site content, move docs to under site/docs (#1489) 2019-05-17 10:56:03 -07:00

README.md

100

Build Status

Overview

Velero (formerly Heptio Ark) gives you tools to back up and restore your Kubernetes cluster resources and persistent volumes. Velero lets you:

  • Take backups of your cluster and restore in case of loss.
  • Copy cluster resources to other clusters.
  • Replicate your production environment for development and testing environments.

Velero consists of:

  • A server that runs on your cluster
  • A command-line client that runs locally

You can run Velero in clusters on a cloud provider or on-premises. For detailed information, see Compatible Storage Providers.

Installation

We strongly recommend that you use an official release of Velero. The tarballs for each release contain the velero command-line client. Follow the installation instructions to get started.

The code and sample YAML files in the master branch of the Velero repository are under active development and are not guaranteed to be stable. Use them at your own risk!

More information

The documentation provides a getting started guide, plus information about building from source, architecture, extending Velero, and more.

Please use the version selector at the top of the site to ensure you are using the appropriate documentation for your version of Velero.

Troubleshooting

If you encounter issues, review the troubleshooting docs, file an issue, or talk to us on the #velero channel on the Kubernetes Slack server.

Contributing

Thanks for taking the time to join our community and start contributing!

Feedback and discussion are available on the mailing list.

Before you start

Pull requests

  • We welcome pull requests. Feel free to dig through the issues and jump in.

Changelog

See the list of releases to find out about feature changes.