36fc42761b
* Add colors to describe command * Add colors to describe backups/restore/schedules commands * Make name in the output bold * Disable colors via `--colorized` flag or if velero isn't in TTY Co-authored-by: Clay Kauzlaric <ckauzlaric@vmware.com> Signed-off-by: Clay Kauzlaric <ckauzlaric@vmware.com> Signed-off-by: Mikael Manukyan <mmanukyan@vmware.com> * Add changelog * and run make update Co-authored-by: Mikael Manukyan <mmanukyan@vmware.com> Signed-off-by: Mikael Manukyan <mmanukyan@vmware.com> Signed-off-by: Clay Kauzlaric <ckauzlaric@vmware.com> * Add colorized to the client config file Co-authored-by: Mikael Manukyan <mmanukyan@vmware.com> Signed-off-by: Clay Kauzlaric <ckauzlaric@vmware.com> Co-authored-by: Mikael Manukyan <mmanukyan@vmware.com> * allow client config to use string values * the command `velero client config set colorized=false` writes a string value of "false" into the config. This change allows that string to be accepted and converted into a boolean when used in program. Signed-off-by: Clay Kauzlaric <ckauzlaric@vmware.com> * Add docs about colored CLI output Co-authored-by: Mikael Manukyan <mmanukyan@vmware.com> Signed-off-by: Clay Kauzlaric <ckauzlaric@vmware.com> * Update site/content/docs/main/customize-installation.md Co-authored-by: JenTing Hsiao <jenting.hsiao@suse.com> Signed-off-by: Clay Kauzlaric <ckauzlaric@vmware.com> * docs: remove comma * as per @carlisia 's suggestion Signed-off-by: Clay Kauzlaric <ckauzlaric@vmware.com> Co-authored-by: Clay Kauzlaric <ckauzlaric@vmware.com> Co-authored-by: Clay Kauzlaric <clay.kauzlaric@gmail.com> Co-authored-by: JenTing Hsiao <jenting.hsiao@suse.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.