Merge pull request #3673 from zubron/release-1.6-changelog-docs
Add changelog and docs for v1.6.0
David L. Smith-Uchida
GitHub
@@ -1,10 +1,8 @@
|
||||
## Current release:
|
||||
* [CHANGELOG-1.5.md][15]
|
||||
|
||||
## Development releases:
|
||||
* [CHANGELOG-1.6.md][16]
|
||||
|
||||
## Older releases:
|
||||
* [CHANGELOG-1.5.md][15]
|
||||
* [CHANGELOG-1.4.md][14]
|
||||
* [CHANGELOG-1.3.md][13]
|
||||
* [CHANGELOG-1.2.md][12]
|
||||
|
||||
@@ -1,17 +1,17 @@
|
||||
## v1.6.0-rc.2
|
||||
### 2021-03-29
|
||||
## v1.6.0
|
||||
### 2021-04-12
|
||||
|
||||
### Download
|
||||
https://github.com/vmware-tanzu/velero/releases/tag/v1.6.0-rc.2
|
||||
https://github.com/vmware-tanzu/velero/releases/tag/v1.6.0
|
||||
|
||||
### Container Image
|
||||
`velero/velero:v1.6.0-rc.2`
|
||||
`velero/velero:v1.6.0`
|
||||
|
||||
### Documentation
|
||||
https://velero.io/docs/v1.6-rc.2/
|
||||
https://velero.io/docs/v1.6/
|
||||
|
||||
### Upgrading
|
||||
https://velero.io/docs/v1.6-rc.2/upgrade-to-1.6/
|
||||
https://velero.io/docs/v1.6/upgrade-to-1.6/
|
||||
|
||||
### Highlights
|
||||
|
||||
@@ -68,4 +68,4 @@ https://velero.io/docs/v1.6-rc.2/upgrade-to-1.6/
|
||||
* Pass annotations from schedule to backup it creates the same way it is done for labels. Add WithannotationsMap function to builder to be able to pass map instead of key/val list (#3067, @funkycode)
|
||||
* Add instructions to clone repository for examples in docs (#3074, @MadhavJivrajani)
|
||||
* 🏃♂️ update setup-kind github actions CI (#3085, @ashish-amarnath)
|
||||
* Modify wrong function name to correct one. (#3106, @shellwedance)
|
||||
* Modify wrong function name to correct one. (#3106, @shellwedance)
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
cli: allow creating multiple instances of Velero across two different namespaces
|
||||
@@ -1 +0,0 @@
|
||||
Feature: It is possible to change the timezone of the container by specifying in the manifest.. env: [TZ: Zone/Country], or in the Helm Chart.. configuration: {extraEnvVars: [TZ: 'Zone/Country']}
|
||||
@@ -1 +0,0 @@
|
||||
Fix issue where bare `velero` command returned an error code.
|
||||
@@ -1 +0,0 @@
|
||||
Restore CRD Resource name to fix CRD wait functionality.
|
||||
@@ -1 +0,0 @@
|
||||
Fixed 'velero.io/change-pvc-node-selector' plugin to fetch configmap using label key "velero.io/change-pvc-node-selector"
|
||||
@@ -1 +0,0 @@
|
||||
Compile with Go 1.15
|
||||
@@ -1 +0,0 @@
|
||||
Fix BSL controller to avoid invoking init() on all BSLs regardless of ValidationFrequency
|
||||
@@ -1 +0,0 @@
|
||||
Fixed an issue where the deletion of a backup would fail if the backup tarball couldn't be downloaded from object storage. Now the tarball is only downloaded if there are associated DeleteItemAction plugins and if downloading the tarball fails, the plugins are skipped.
|
||||
@@ -1 +0,0 @@
|
||||
Ensure that bound PVCs and PVs remain bound on restore.
|
||||
@@ -1,2 +0,0 @@
|
||||
Allows the restic-wait container to exist in any order in the pod being restored.
|
||||
Prints a warning message in the case where the restic-wait container isn't the first container in the list of initialization containers.
|
||||
@@ -1 +0,0 @@
|
||||
Add warning to velero version cmd if the client and server versions mismatch.
|
||||
@@ -1 +0,0 @@
|
||||
🐛 Use namespace and name to match PVB to Pod restore
|
||||
@@ -1 +0,0 @@
|
||||
Fixed various typos across codebase
|
||||
@@ -1 +0,0 @@
|
||||
🐛 ItemAction plugins for unresolvable types should not be run for all types
|
||||
@@ -1,2 +0,0 @@
|
||||
Basic end-to-end tests, generate data/backup/remove/restore/verify
|
||||
Uses distributed data generator
|
||||
@@ -1 +0,0 @@
|
||||
Added GitHub Workflow running Codespell for spell checking
|
||||
@@ -1,2 +0,0 @@
|
||||
Pass annotations from schedule to backup it creates the same way it is done for labels
|
||||
Add WithannotationsMap function to builder to be able to pass map instead of key/val list
|
||||
@@ -1 +0,0 @@
|
||||
feat: add delete sub-command for BSL
|
||||
@@ -1 +0,0 @@
|
||||
Add instructions to clone repository for examples in docs
|
||||
@@ -1 +0,0 @@
|
||||
🐛 BSLs with validation disabled should be validated at least once
|
||||
@@ -1 +0,0 @@
|
||||
🏃♂️ update setup-kind github actions CI
|
||||
@@ -1 +0,0 @@
|
||||
feat: support configures BackupStorageLocation custom resources to indicate which one is the default
|
||||
@@ -1 +0,0 @@
|
||||
Added "--preserve-nodeports" flag to preserve original nodePorts when restoring.
|
||||
@@ -1 +0,0 @@
|
||||
Modify wrong function name to correct one.
|
||||
@@ -1 +0,0 @@
|
||||
Progress reporting added for Velero Restores
|
||||
@@ -1 +0,0 @@
|
||||
Owner reference in backup when created from schedule
|
||||
@@ -1,2 +0,0 @@
|
||||
Restore API group version by priority
|
||||
Increase timeout to 3 minutes in DeploymentIsReady(...) function in the install package
|
||||
@@ -1 +0,0 @@
|
||||
feat: support setting BackupStorageLocation CA certificate via `velero backup-location set --cacert`
|
||||
@@ -1 +0,0 @@
|
||||
Set the BSL created at install time as the "default"
|
||||
@@ -1 +0,0 @@
|
||||
issue: add flag to the schedule cmd to configure the `useOwnerReferencesInBackup` option #3176
|
||||
@@ -1 +0,0 @@
|
||||
Add field and cli flag to associate a credential with a BSL on BSL create|set.
|
||||
@@ -1 +0,0 @@
|
||||
Add restic initContainer length check in pod volume restore to prevent restic plugin container disappear in runtime
|
||||
@@ -1 +0,0 @@
|
||||
Bump versions of external snapshotter and others in order to make `go get` to succeed
|
||||
@@ -1 +0,0 @@
|
||||
Capitalize all help messages
|
||||
@@ -1 +0,0 @@
|
||||
Support fish shell completion
|
||||
@@ -1 +0,0 @@
|
||||
Increased default Velero pod memory limit to 512Mi
|
||||
@@ -1 +0,0 @@
|
||||
Add colored output to `describe schedule/backup/restore` commands
|
||||
@@ -1 +0,0 @@
|
||||
Change the logging level of PV deletion timeout from Debug to Warn
|
||||
@@ -1 +0,0 @@
|
||||
Add uninstall option for velero cli
|
||||
@@ -1 +0,0 @@
|
||||
Add support for per-BSL credentials. Velero will now serialize the secret referenced by the `Credential` field in the BSL and pass this path through to Object Storage plugins via the `config` map using the `credentialsFile` key.
|
||||
@@ -1 +0,0 @@
|
||||
Add CAPI Cluster and ClusterResourceSets to default restore priorities so that the capi-controller-manager does not panic on restores.
|
||||
@@ -1 +0,0 @@
|
||||
Use label to select Velero deployment in plugin cmd
|
||||
@@ -1 +0,0 @@
|
||||
Fixed a bug where restic volumes would not be restored when using a namespace mapping.
|
||||
@@ -1 +0,0 @@
|
||||
Add support for restic to use per-BSL credentials. Velero will now serialize the secret referenced by the `Credential` field in the BSL and use this path when setting provider specific environment variables for restic commands.
|
||||
@@ -1 +0,0 @@
|
||||
Upgrade restic from v0.9.6 to v0.12.0.
|
||||
@@ -12,10 +12,10 @@ params:
|
||||
hero:
|
||||
backgroundColor: med-blue
|
||||
versioning: true
|
||||
latest: v1.5
|
||||
latest: v1.6
|
||||
versions:
|
||||
- main
|
||||
- v1.6-rc.2
|
||||
- v1.6
|
||||
- v1.5
|
||||
- v1.4
|
||||
- v1.3.2
|
||||
|
||||
@@ -29,7 +29,7 @@ If you're not yet running at least Velero v1.5, see the following:
|
||||
|
||||
```bash
|
||||
Client:
|
||||
Version: v1.6.0-rc.2
|
||||
Version: v1.6.0
|
||||
Git commit: <git SHA>
|
||||
```
|
||||
|
||||
@@ -45,12 +45,12 @@ If you're not yet running at least Velero v1.5, see the following:
|
||||
|
||||
```bash
|
||||
kubectl set image deployment/velero \
|
||||
velero=velero/velero:v1.6.0-rc.2 \
|
||||
velero=velero/velero:v1.6.0 \
|
||||
--namespace velero
|
||||
|
||||
# optional, if using the restic daemon set
|
||||
kubectl set image daemonset/restic \
|
||||
restic=velero/velero:v1.6.0-rc.2 \
|
||||
restic=velero/velero:v1.6.0 \
|
||||
--namespace velero
|
||||
```
|
||||
|
||||
@@ -64,11 +64,11 @@ If you're not yet running at least Velero v1.5, see the following:
|
||||
|
||||
```bash
|
||||
Client:
|
||||
Version: v1.6.0-rc.2
|
||||
Version: v1.6.0
|
||||
Git commit: <git SHA>
|
||||
|
||||
Server:
|
||||
Version: v1.6.0-rc.2
|
||||
Version: v1.6.0
|
||||
```
|
||||
|
||||
## Notes
|
||||
@@ -86,4 +86,4 @@ After upgrading, if there is a previously created backup storage location with t
|
||||
[6]: https://github.com/vmware-tanzu/velero/releases/tag/v1.4.2
|
||||
[7]: https://github.com/vmware-tanzu/velero/issues/2077
|
||||
[8]: https://github.com/vmware-tanzu/velero/issues/2311
|
||||
[9]: https://velero.io/docs/v1.6-rc.2/locations
|
||||
[9]: https://velero.io/docs/v1.6/locations
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
toc: "false"
|
||||
cascade:
|
||||
version: v1.6-rc.2
|
||||
version: v1.6
|
||||
toc: "true"
|
||||
---
|
||||
![100]
|
||||
@@ -33,7 +33,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.6-rc.2/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.6/start-contributing/) documentation for guidance on how to setup Velero for development.
|
||||
|
||||
## Changelog
|
||||
|
||||
@@ -88,5 +88,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.6-rc.2/examples/nginx-app/with-pv.yaml
|
||||
[2]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/examples/nginx-app/with-pv.yaml
|
||||
[3]: cloud-common.md
|
||||
@@ -70,7 +70,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.6-rc.2/pkg/restic/mocks/restorer.go
|
||||
Example: if you want to change this mock: https://github.com/vmware-tanzu/velero/blob/v1.6.0/pkg/restic/mocks/restorer.go
|
||||
|
||||
Run:
|
||||
|
||||
|
Before Width: | Height: | Size: 130 KiB After Width: | Height: | Size: 130 KiB |
|
Before Width: | Height: | Size: 73 KiB After Width: | Height: | Size: 73 KiB |
|
Before Width: | Height: | Size: 32 KiB After Width: | Height: | Size: 32 KiB |
|
Before Width: | Height: | Size: 407 KiB After Width: | Height: | Size: 407 KiB |
|
Before Width: | Height: | Size: 285 KiB After Width: | Height: | Size: 285 KiB |
|
Before Width: | Height: | Size: 64 KiB After Width: | Height: | Size: 64 KiB |
|
Before Width: | Height: | Size: 277 KiB After Width: | Height: | Size: 277 KiB |
|
Before Width: | Height: | Size: 123 KiB After Width: | Height: | Size: 123 KiB |
|
Before Width: | Height: | Size: 83 KiB After Width: | Height: | Size: 83 KiB |
|
Before Width: | Height: | Size: 48 KiB After Width: | Height: | Size: 48 KiB |
@@ -244,5 +244,5 @@ After creating the Velero server in your cluster, try this example:
|
||||
|
||||
## Additional Reading
|
||||
|
||||
* [Official Velero Documentation](https://velero.io/docs/v1.6-rc.2/)
|
||||
* [Official Velero Documentation](https://velero.io/docs/v1.6/)
|
||||
* [Oracle Cloud Infrastructure Documentation](https://docs.cloud.oracle.com/)
|
||||
@@ -113,5 +113,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.6-rc.2/pkg/plugin/logger.go
|
||||
[3]: https://github.com/vmware-tanzu/velero/blob/v1.6-rc.2/pkg/restore/restic_restore_action.go
|
||||
[2]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/pkg/plugin/logger.go
|
||||
[3]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/pkg/restore/restic_restore_action.go
|
||||
@@ -365,4 +365,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.6-rc.2/pkg/apis/velero/v1/constants.go
|
||||
[11]: https://github.com/vmware-tanzu/velero/blob/v1.6.0/pkg/apis/velero/v1/constants.go
|
||||
|
Before Width: | Height: | Size: 33 KiB After Width: | Height: | Size: 33 KiB |
|
Before Width: | Height: | Size: 56 KiB After Width: | Height: | Size: 56 KiB |
|
Before Width: | Height: | Size: 85 KiB After Width: | Height: | Size: 85 KiB |
|
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 41 KiB |
|
Before Width: | Height: | Size: 68 KiB After Width: | Height: | Size: 68 KiB |
|
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 44 KiB |
@@ -4,7 +4,7 @@ layout: docs
|
||||
toc: "true"
|
||||
---
|
||||
|
||||
There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.6-rc.2/GOVERNANCE.md#code-repositories).
|
||||
There are some guidelines maintainers need to follow. We list them here for quick reference, especially for new maintainers. These guidelines apply to all projects in the Velero org, including the main project, the Velero Helm chart, and all other [related repositories](https://github.com/vmware-tanzu/velero/blob/v1.6.0/GOVERNANCE.md#code-repositories).
|
||||
|
||||
Please be sure to also go through the guidance under the entire [Contribute](start-contributing/) section.
|
||||
|
||||
@@ -14,12 +14,12 @@ Please be sure to also go through the guidance under the entire [Contribute](sta
|
||||
- As you review a PR that is not yet ready to merge, please check if the "request review" needs to be refreshed for any reviewer (this is better than @mention at them)
|
||||
- Refrain from @mention other maintainers to review the PR unless it is an immediate need. All maintainers already get notified through the automated add to the "request review". If it is an urgent need, please add a helpful message as to why it is so people can properly prioritize work.
|
||||
- There is no need to manually request reviewers: after the PR is created, all maintainers will be automatically added to the list (note: feel free to remove people if they are on PTO, etc).
|
||||
- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.6-rc.2/GOVERNANCE.md#lazy-consensus) policy for the project.
|
||||
- Be familiar with the [lazy consensus](https://github.com/vmware-tanzu/velero/blob/v1.6.0/GOVERNANCE.md#lazy-consensus) policy for the project.
|
||||
|
||||
Some tips for doing reviews:
|
||||
- There are some [code standards and general guidelines](https://velero.io/docs/v1.6-rc.2/code-standards) we aim for
|
||||
- We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.6-rc.2/style-guide/)
|
||||
- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.6-rc.2/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder.
|
||||
- There are some [code standards and general guidelines](https://velero.io/docs/v1.6/code-standards) we aim for
|
||||
- We have [guidelines for writing and reviewing documentation](https://velero.io/docs/v1.6/style-guide/)
|
||||
- When reviewing a design document, ensure it follows [our format and guidelines]( https://github.com/vmware-tanzu/velero/blob/v1.6.0/design/_template.md). Also, when reviewing a PR that implements a previously accepted design, ensure the associated design doc is moved to the [design/implemented](https://github.com/vmware-tanzu/velero/tree/main/design/implemented) folder.
|
||||
|
||||
|
||||
## Creating a release
|
||||
@@ -32,4 +32,4 @@ Maintainers are expected to participate in the community support rotation. We ha
|
||||
Maintainers for the Velero project are highly involved with the open source community. All the online community meetings for the project are listed in our [community](community) page.
|
||||
|
||||
## How do I become a maintainer?
|
||||
The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.6-rc.2/GOVERNANCE.md#maintainers) is decided.
|
||||
The Velero project welcomes contributors of all kinds. We are also always on the look out for a high level of engagement from contributors and opportunities to bring in new maintainers. If this is of interest, take a look at how [adding a maintainer](https://github.com/vmware-tanzu/velero/blob/v1.6.0/GOVERNANCE.md#maintainers) is decided.
|
||||