mirror of
https://github.com/vmware-tanzu/velero.git
synced 2026-01-09 22:47:27 +00:00
v1.4.0 changelog and docs (#2577)
* Add changelog for v1.4.0 Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Add v1.4.0 docs Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Fix broken CI, links, and date Signed-off-by: Nolan Brubaker <brubakern@vmware.com> * Fix duplicate and missing TOC info Signed-off-by: Nolan Brubaker <brubakern@vmware.com>
This commit is contained in:
Nolan Brubaker
GitHub
@@ -1,11 +1,11 @@
|
||||
## Current release:
|
||||
* [CHANGELOG-1.3.md][13]
|
||||
* [CHANGELOG-1.4.md][14]
|
||||
|
||||
## Development release:
|
||||
* [CHANGELOG-1.4.md][14]
|
||||
* [Unreleased Changes][0]
|
||||
|
||||
## Older releases:
|
||||
* [CHANGELOG-1.3.md][13]
|
||||
* [CHANGELOG-1.2.md][12]
|
||||
* [CHANGELOG-1.1.md][11]
|
||||
* [CHANGELOG-1.0.md][10]
|
||||
|
||||
@@ -1,53 +1,54 @@
|
||||
## v1.4.0-beta.1
|
||||
### 2020-05-08
|
||||
## v1.4.0
|
||||
### 2020-05-26
|
||||
|
||||
### Download
|
||||
https://github.com/vmware-tanzu/velero/releases/tag/v1.4.0-beta.1
|
||||
https://github.com/vmware-tanzu/velero/releases/tag/v1.4.0
|
||||
|
||||
### Container Image
|
||||
`velero/velero:v1.4.0-beta.1`
|
||||
`velero/velero:v1.4.0`
|
||||
|
||||
### Documentation
|
||||
https://velero.io/docs/v1.4-pre/
|
||||
https://velero.io/docs/v1.4/
|
||||
|
||||
### Upgrading
|
||||
https://velero.io/docs/v1.4-pre/upgrade-to-1.4/
|
||||
|
||||
### Download
|
||||
https://github.com/vmware-tanzu/velero/releases/tag/v1.4.0-beta.1
|
||||
https://velero.io/docs/v1.4/upgrade-to-1.4/
|
||||
|
||||
### Highlights
|
||||
|
||||
* Added beta-level CSI support
|
||||
* Added beta-level CSI support!
|
||||
* Added custom CA certificate support
|
||||
* Backup progress reporting
|
||||
* Changed backup tarball format to support all versions of a given resource
|
||||
|
||||
### All Changes
|
||||
* increment restic volumesnapshot count after successful pvb create (#2542, @ashish-amarnath)
|
||||
* Add details of CSI volumesnapshotcontents associated with a backup to `velero backup describe` when the `EnableCSI` feature flag is given on the velero client. (#2448, @nrb)
|
||||
* report backup progress (number of items backed up so far out of an estimated total number of items) during backup in the logs and as status fields on the Backup custom resource (#2440, @skriss)
|
||||
* allow feature flags to be passed from install CLI (#2503, @ashish)
|
||||
* sync backups' CSI API objects into the cluster as part of the backup sync controller (#2496, @ashish)
|
||||
* Allow users the option to retrieve all versions of a given resource (instead of just the preferred version) from the API server with the `EnableAPIGroupVersions` feature flag. (#2373, @brito-rafa)
|
||||
* Changed backup tarball format to store all versions of a given resource, updated backup tarball format to 1.1.0. (#2373, @brito-rafa)
|
||||
* allow feature flags to be passed from install CLI (#2503, @ashish-amarnath)
|
||||
* sync backups' CSI API objects into the cluster as part of the backup sync controller (#2496, @ashish-amarnath)
|
||||
* bug fix: in error location logging hook, if the item logged under the `error` key doesn't implement the `error` interface, don't return an error since this is a valid scenario (#2487, @skriss)
|
||||
* bug fix: in CRD restore plugin, don't use runtime.DefaultUnstructuredConverter.FromUnstructured(...) to avoid conversion issues when float64 fields contain int values (#2484, @skriss)
|
||||
* during backup deletion also delete CSI volumesnapshotcontents that were created as a part of the backup but the associated volumesnapshot object does not exist (#2480, @ashish)
|
||||
* during backup deletion also delete CSI volumesnapshotcontents that were created as a part of the backup but the associated volumesnapshot object does not exist (#2480, @ashish-amarnath)
|
||||
* If plugins don't support the `--features` flag, don't pass it to them. Also, update the standard plugin server to ignore unknown flags. (#2479, @skriss)
|
||||
* At backup time, if a CustomResourceDefinition appears to have been created via the v1beta1 endpoint, retrieve it from the v1beta1 endpoint instead of simply changing the APIVersion. (#2478, @nrb)
|
||||
* update container base images from ubuntu:bionic to ubuntu:focal (#2471, @skriss)
|
||||
* bug fix: when a resource includes/excludes list contains unresolvable items, don't remove them from the list, so that the list doesn't inadvertently end up matching *all* resources. (#2462, @skriss)
|
||||
* Azure: add support for getting storage account key for restic directly from an environment variable (#2455, @jaygridley)
|
||||
* Support to skip VSL validation for the backup having SnapshotVolumes set to false or created with `--snapshot-volumes=false` (#2450, @mynktl)
|
||||
* during backup deletion also delete CSI volumesnapshots that were created as a part of the backup (#2411, @ashish)
|
||||
* clarify the wording for restore describe for namespaces included Instead of showing it as "*" explicitly mention that all the namespaces from the backup object are included. (#1918, @raghavendrabhat)
|
||||
* When the EnableCSI feature flag is provided, upload CSI VolumeSnapshots and VolumeSnapshotContents to object storage as gzipped JSON. (#2323, @nrb)
|
||||
* report backup progress (number of items backed up so far out of an estimated total number of items) during backup in the logs and as status fields on the Backup custom resource (#2440, @skriss)
|
||||
* bug fix: populate namespace in logs for backup errors (#2438, @skriss)
|
||||
* bug fix: save PodVolumeBackup manifests to object storage even if the volume was empty, so that on restore, the PV is dynamically reprovisioned if applicable (#2390, @skriss)
|
||||
* adding annotations on backup CRD for k8s major, minor and git versions (#2346, @brito)
|
||||
* during backup deletion also delete CSI volumesnapshots that were created as a part of the backup (#2411, @ashish-amarnath)
|
||||
* bump Kubernetes module dependencies to v0.17.4 to get fix for https://github.com/kubernetes/kubernetes/issues/86149 (#2407, @skriss)
|
||||
* bug fix: save PodVolumeBackup manifests to object storage even if the volume was empty, so that on restore, the PV is dynamically reprovisioned if applicable (#2390, @skriss)
|
||||
* Adding new restoreItemAction for PVC to update the selected-node annotation (#2377, @mynktl)
|
||||
* Added a --cacert flag to the install command to provide the CA bundle to use when verifying TLS connections to object storage (#2368, @mansam)
|
||||
* Added a `--cacert` flag to the velero client describe, download, and logs commands to allow passing a path to a certificate to use when verifying TLS connections to object storage. Also added a corresponding client config option called `cacert` which takes a path to a certificate bundle to use as a default when `--cacert` is not specified. (#2364, @mansam)
|
||||
* support setting a custom CA certificate on a BSL to use when verifying TLS connections (#2353, @mansam)
|
||||
* add CSI snapshot API types into default restore priorities (#2318, @ashish)
|
||||
* adding annotations on backup CRD for k8s major, minor and git versions (#2346, @brito-rafa)
|
||||
* When the EnableCSI feature flag is provided, upload CSI VolumeSnapshots and VolumeSnapshotContents to object storage as gzipped JSON. (#2323, @nrb)
|
||||
* add CSI snapshot API types into default restore priorities (#2318, @ashish-amarnath)
|
||||
* refactoring: wait for all informer caches to sync before running controllers (#2299, @skriss)
|
||||
* refactor restore code to lazily resolve resources via discovery and eliminate second restore loop for instances of restored CRDs (#2248, @skriss)
|
||||
* upgrade to go 1.14 and migrate from `dep` to go modules (#2214, @skriss)
|
||||
* clarify the wording for restore describe for namespaces included
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
clarify the wording for restore describe for namespaces included
|
||||
|
||||
Instead of showing it as "*" explicitly mention that all the namespaces
|
||||
from the backup object are included.
|
||||
@@ -1 +0,0 @@
|
||||
upgrade to go 1.14 and migrate from `dep` to go modules
|
||||
@@ -1 +0,0 @@
|
||||
refactor restore code to lazily resolve resources via discovery and eliminate second restore loop for instances of restored CRDs
|
||||
@@ -1 +0,0 @@
|
||||
refactoring: wait for all informer caches to sync before running controllers
|
||||
@@ -1 +0,0 @@
|
||||
add CSI snapshot API types into default restore priorities
|
||||
@@ -1 +0,0 @@
|
||||
When the EnableCSI feature flag is provided, upload CSI VolumeSnapshots and VolumeSnapshotContents to object storage as gzipped JSON.
|
||||
@@ -1 +0,0 @@
|
||||
adding annotations on backup CRD for k8s major, minor and git versions
|
||||
@@ -1 +0,0 @@
|
||||
support setting a custom CA certificate on a BSL to use when verifying TLS connections
|
||||
@@ -1 +0,0 @@
|
||||
Added a `--cacert` flag to the velero client describe, download, and logs commands to allow passing a path to a certificate to use when verifying TLS connections to object storage. Also added a corresponding client config option called `cacert` which takes a path to a certificate bundle to use as a default when `--cacert` is not specified.
|
||||
@@ -1 +0,0 @@
|
||||
Added a --cacert flag to the install command to provide the CA bundle to use when verifying TLS connections to object storage
|
||||
@@ -1,2 +0,0 @@
|
||||
Allow users the option to retrieve all versions of a given resource (instead of just the preferred version) from the API server with the `EnableAPIGroupVersions` feature flag.
|
||||
* Changed backup tarball format to store all versions of a given resource, updated backup tarball format to 1.1.0.
|
||||
@@ -1 +0,0 @@
|
||||
Adding new restoreItemAction for PVC to update the selected-node annotation
|
||||
@@ -1 +0,0 @@
|
||||
bug fix: save PodVolumeBackup manifests to object storage even if the volume was empty, so that on restore, the PV is dynamically reprovisioned if applicable
|
||||
@@ -1 +0,0 @@
|
||||
bump Kubernetes module dependencies to v0.17.4 to get fix for https://github.com/kubernetes/kubernetes/issues/86149
|
||||
@@ -1 +0,0 @@
|
||||
during backup deletion also delete CSI volumesnapshots that were created as a part of the backup
|
||||
@@ -1 +0,0 @@
|
||||
bug fix: populate namespace in logs for backup errors
|
||||
@@ -1 +0,0 @@
|
||||
report backup progress (number of items backed up so far out of an estimated total number of items) during backup in the logs and as status fields on the Backup custom resource
|
||||
@@ -1 +0,0 @@
|
||||
Add details of CSI volumesnapshotcontents associated with a backup to `velero backup describe` when the `EnableCSI` feature flag is given on the velero client.
|
||||
@@ -1 +0,0 @@
|
||||
Support to skip VSL validation for the backup having SnapshotVolumes set to false or created with `--snapshot-volumes=false`
|
||||
@@ -1 +0,0 @@
|
||||
Azure: add support for getting storage account key for restic directly from an environment variable
|
||||
@@ -1 +0,0 @@
|
||||
bug fix: when a resource includes/excludes list contains unresolvable items, don't remove them from the list, so that the list doesn't inadvertently end up matching *all* resources.
|
||||
@@ -1 +0,0 @@
|
||||
update container base images from ubuntu:bionic to ubuntu:focal
|
||||
@@ -1 +0,0 @@
|
||||
At backup time, if a CustomResourceDefinition appears to have been created via the v1beta1 endpoint, retrieve it from the v1beta1 endpoint instead of simply changing the APIVersion.
|
||||
@@ -1 +0,0 @@
|
||||
If plugins don't support the `--features` flag, don't pass it to them. Also, update the standard plugin server to ignore unknown flags.
|
||||
@@ -1 +0,0 @@
|
||||
during backup deletion also delete CSI volumesnapshotcontents that were created as a part of the backup but the associated volumesnapshot object does not exist
|
||||
@@ -1 +0,0 @@
|
||||
bug fix: in CRD restore plugin, don't use runtime.DefaultUnstructuredConverter.FromUnstructured(...) to avoid conversion issues when float64 fields contain int values
|
||||
@@ -1 +0,0 @@
|
||||
bug fix: in error location logging hook, if the item logged under the `error` key doesn't implement the `error` interface, don't return an error since this is a valid scenario
|
||||
@@ -1 +0,0 @@
|
||||
sync backups' CSI API objects into the cluster as part of the backup sync controller
|
||||
@@ -1 +0,0 @@
|
||||
allow feature flags to be passed from install CLI
|
||||
@@ -1 +0,0 @@
|
||||
increment restic volumesnapshot count after successful pvb create
|
||||
@@ -56,10 +56,10 @@ defaults:
|
||||
gh: https://github.com/vmware-tanzu/velero/tree/master
|
||||
layout: "docs"
|
||||
- scope:
|
||||
path: docs/v1.4-pre
|
||||
path: docs/v1.4
|
||||
values:
|
||||
version: v1.4-pre
|
||||
gh: https://github.com/vmware-tanzu/velero/tree/v1.4.0-beta.1
|
||||
version: v1.4
|
||||
gh: https://github.com/vmware-tanzu/velero/tree/v1.4.0
|
||||
layout: "docs"
|
||||
- scope:
|
||||
path: docs/v1.3.2
|
||||
@@ -176,10 +176,10 @@ collections:
|
||||
- plugin-list
|
||||
|
||||
versioning: true
|
||||
latest: v1.3.2
|
||||
latest: v1.4
|
||||
versions:
|
||||
- master
|
||||
- v1.4-pre
|
||||
- v1.4
|
||||
- v1.3.2
|
||||
- v1.3.1
|
||||
- v1.3.0
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
# that the navigation for older versions still work.
|
||||
|
||||
master: master-toc
|
||||
v1.4-pre: v1-4-pre-toc
|
||||
v1.4: v1-4-toc
|
||||
v1.3.2: v1-3-2-toc
|
||||
v1.3.1: v1-3-1-toc
|
||||
v1.3.0: v1-3-0-toc
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
|
||||
## 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 cloud provider or on-premises. Velero lets you:
|
||||
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.
|
||||
@@ -27,7 +27,7 @@ If you encounter issues, review the [troubleshooting docs][30], [file an issue][
|
||||
|
||||
## Contributing
|
||||
|
||||
If you are ready to jump in and test, add code, or help with documentation, follow the instructions on our [Start contributing](https://velero.io/docs/v1.4.0-beta.1/start-contributing/) documentation for guidance on how to setup Velero for development.
|
||||
If you are ready to jump in and test, add code, or help with documentation, follow the instructions on our [Start contributing](https://velero.io/docs/v1.4/start-contributing/) documentation for guidance on how to setup Velero for development.
|
||||
|
||||
## Changelog
|
||||
|
||||
@@ -52,7 +52,7 @@ Example:
|
||||
|
||||
We use a package to generate mocks for our interfaces.
|
||||
|
||||
Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.4.0-beta.1/pkg/restic/mocks/restorer.go
|
||||
Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.4.0/pkg/restic/mocks/restorer.go
|
||||
|
||||
Run:
|
||||
|
||||
@@ -241,5 +241,5 @@ After creating the Velero server in your cluster, try this example:
|
||||
|
||||
## Additional Reading
|
||||
|
||||
* [Official Velero Documentation](https://velero.io/docs/v1.4.0-beta.1/)
|
||||
* [Official Velero Documentation](https://velero.io/docs/v1.4/)
|
||||
* [Oracle Cloud Infrastructure Documentation](https://docs.cloud.oracle.com/)
|
||||
@@ -87,5 +87,5 @@ Once parsed into a `[]string`, the features can then be registered using the `Ne
|
||||
Velero adds the `LD_LIBRARY_PATH` into the list of environment variables to provide the convenience for plugins that requires C libraries/extensions in the runtime.
|
||||
|
||||
[1]: https://github.com/vmware-tanzu/velero-plugin-example
|
||||
[2]: https://github.com/vmware-tanzu/velero/blob/v1.4.0-beta.1/pkg/plugin/logger.go
|
||||
[3]: https://github.com/vmware-tanzu/velero/blob/v1.4.0-beta.1/pkg/restore/restic_restore_action.go
|
||||
[2]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/pkg/plugin/logger.go
|
||||
[3]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/pkg/restore/restic_restore_action.go
|
||||
@@ -295,4 +295,4 @@ If you get an error like `complete:13: command not found: compdef`, then add the
|
||||
[8]: https://github.com/vmware-tanzu/velero/issues/2311
|
||||
[9]: self-signed-certificates.md
|
||||
[10]: csi.md
|
||||
[11]: https://github.com/vmware-tanzu/velero/blob/v1.4.0-beta.1/pkg/apis/velero/v1/constants.go
|
||||
[11]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/pkg/apis/velero/v1/constants.go
|
||||
@@ -22,7 +22,7 @@ Examples of cases where Velero is useful:
|
||||
|
||||
Yes, with some exceptions. For example, when Velero restores pods it deletes the `nodeName` from the
|
||||
pod so that it can be scheduled onto a new node. You can see some more examples of the differences
|
||||
in [pod_action.go](https://github.com/vmware-tanzu/velero/blob/v1.4.0-beta.1/pkg/restore/pod_action.go)
|
||||
in [pod_action.go](https://github.com/vmware-tanzu/velero/blob/v1.4.0/pkg/restore/pod_action.go)
|
||||
|
||||
## I'm using Velero in multiple clusters. Should I use the same bucket to store all of my backups?
|
||||
|
||||
@@ -85,5 +85,5 @@ To use multiple commands, wrap your target command in a shell and separate them
|
||||
|
||||
|
||||
[1]: api-types/backup.md
|
||||
[2]: https://github.com/vmware-tanzu/velero/blob/v1.4.0-beta.1/examples/nginx-app/with-pv.yaml
|
||||
[2]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/examples/nginx-app/with-pv.yaml
|
||||
[3]: cloud-common.md
|
||||
|
Before Width: | Height: | Size: 33 KiB After Width: | Height: | Size: 33 KiB |
|
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 44 KiB |
@@ -17,5 +17,5 @@ Please browse our list of resources, including a playlist of past online communi
|
||||
|
||||
If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`.
|
||||
|
||||
[1]: https://github.com/vmware-tanzu/velero/blob/v1.4.0-beta.1/CODE_OF_CONDUCT.md
|
||||
[2]: https://github.com/vmware-tanzu/velero/blob/v1.4.0-beta.1/CONTRIBUTING.md
|
||||
[1]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/CODE_OF_CONDUCT.md
|
||||
[2]: https://github.com/vmware-tanzu/velero/blob/v1.4.0/CONTRIBUTING.md
|
||||
@@ -24,7 +24,7 @@ If you're not yet running at least Velero v1.3, see the following:
|
||||
|
||||
```bash
|
||||
Client:
|
||||
Version: v1.4.0-beta.1
|
||||
Version: v1.4.0
|
||||
Git commit: <git SHA>
|
||||
```
|
||||
|
||||
@@ -32,12 +32,12 @@ If you're not yet running at least Velero v1.3, see the following:
|
||||
|
||||
```bash
|
||||
kubectl set image deployment/velero \
|
||||
velero=velero/velero:v1.4.0-beta.1 \
|
||||
velero=velero/velero:v1.4.0 \
|
||||
--namespace velero
|
||||
|
||||
# optional, if using the restic daemon set
|
||||
kubectl set image daemonset/restic \
|
||||
restic=velero/velero:v1.4.0-beta.1 \
|
||||
restic=velero/velero:v1.4.0 \
|
||||
--namespace velero
|
||||
```
|
||||
|
||||
@@ -57,11 +57,11 @@ If you're not yet running at least Velero v1.3, see the following:
|
||||
|
||||
```bash
|
||||
Client:
|
||||
Version: v1.4.0-beta.1
|
||||
Version: v1.4.0
|
||||
Git commit: <git SHA>
|
||||
|
||||
Server:
|
||||
Version: v1.4.0-beta.1
|
||||
Version: v1.4.0
|
||||
```
|
||||
|
||||
[0]: basic-install.md#install-the-cli
|
||||
@@ -18,7 +18,7 @@ Alternatively, for quickly loading the website, under the `velero/site/` directo
|
||||
bundle exec jekyll serve --livereload --future
|
||||
```
|
||||
|
||||
For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/vmware-tanzu/velero/blob/v1.4.0-beta.1/site/README-JEKYLL.md).
|
||||
For more information on how to run the website locally, please see our [jekyll documentation](https://github.com/vmware-tanzu/velero/blob/v1.4.0/site/README-JEKYLL.md).
|
||||
|
||||
## Adding a blog post
|
||||
|
||||
Reference in New Issue
Block a user