d09b4d60bb
As long as a milestone and the board have the same title, then this workflow should take care of adding an issue into the GitHub Project board when an existing issue is given a milestone. It does NOT support checking for a milestone when an issue is edited or created though, due to limitations on GitHub Actions syntax right now - there's not a great way to validate against an empty `milestone` object at the moment, per https://docs.github.com/en/free-pro-team@latest/actions/reference/context-and-expression-syntax-for-github-actions Signed-off-by: Nolan Brubaker <brubakern@vmware.com> Signed-off-by: Nolan Brubaker <brubakern@vmware.com> |
||
|---|---|---|
| .github | ||
| changelogs | ||
| cmd | ||
| config | ||
| design | ||
| examples | ||
| hack | ||
| internal | ||
| pkg | ||
| site | ||
| test/e2e | ||
| third_party/kubernetes/pkg/kubectl/cmd | ||
| tilt-resources | ||
| .dockerignore | ||
| .gitignore | ||
| .goreleaser.yml | ||
| ADOPTERS.md | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| GOVERNANCE.md | ||
| LICENSE | ||
| MAINTAINERS.md | ||
| Makefile | ||
| PROJECT | ||
| README.md | ||
| ROADMAP.md | ||
| SECURITY.md | ||
| SUPPORT.md | ||
| Tiltfile | ||
| go.mod | ||
| go.sum | ||
| golangci.yaml | ||
| netlify.toml | ||
| restore-hooks_product-requirements.md | ||
README.md
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.