Daniel Jiang d08c4bae4d Refine tag-release.sh
This commit makes several changes to `tag-release.sh` according to the
change in release process:
1. It will support a "ON_RELEASE_BRANCH" param passed via env variable.
   When it's set to "TRUE". The release will be created on the commit of
   branch like `release-xxx`.  This enables us to create release branch
   before GA and tag RC release.
2. It removes the code to push a new branch to upstream.  This is
   because we decided to create branch manually.  For patch releases, we
   will not push the change to release branch, instead, we will make
   sure the release branch has all commits cherrypicked BEFORE we run
   this script to tag the release.

After the change the script will focus on only tag the release, not
making other code change to release branches.

Signed-off-by: Daniel Jiang <jiangd@vmware.com>
2021-09-22 21:20:03 +08:00
2021-08-30 18:37:18 -07:00
2021-04-19 13:45:09 -07:00
2021-09-22 21:20:03 +08:00
2021-08-30 18:37:18 -07:00
2021-09-22 21:20:03 +08:00
2021-08-30 18:37:18 -07:00
2021-09-07 23:03:12 -04:00
2021-08-30 18:37:18 -07:00
2021-08-30 18:37:18 -07:00
2020-06-30 12:51:10 -04:00
2017-08-02 13:27:17 -04:00
2021-09-08 13:16:53 +00:00
2020-09-16 17:56:47 -04:00
2021-08-20 09:05:03 -04:00
2021-07-29 23:56:08 -07:00

100

Build Status CII Best Practices

Overview

Velero (formerly Heptio Ark) gives you tools to back up and restore your Kubernetes cluster resources and persistent volumes. You can run Velero with a public cloud platform or on-premises. Velero lets you:

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

Velero consists of:

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

Documentation

The documentation provides a getting started guide and 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

If you are ready to jump in and test, add code, or help with documentation, follow the instructions on our Start contributing documentation for guidance on how to setup Velero for development.

Changelog

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

Description
No description provided
Readme Apache-2.0 111 MiB
Languages
Go 97.8%
Shell 0.6%
HTML 0.4%
SCSS 0.4%
Makefile 0.4%
Other 0.3%