Specify the "--snapshot-volumes=false" option explicitly when running backup with Restic

If the "--snapshot-volumes=false" isn't specified explicitly, the vSphere plugin will always take snapshots for the volumes even though the "--default-volumes-to-restic" is specified
This can be removed if the logic of vSphere plugin changes
Signed-off-by: Wenkai Yin(尹文开) <yinw@vmware.com>

To improve the reproducibility of the images of velero, this commit pins
the golang and distroless images to specific tag and digest.
Signed-off-by: Daniel Jiang <jiangd@vmware.com>

In upgrade test, both original and to-be-upgrading velero installation should use the compatible plugins, but currently, plugin value is determined by provider.
Signed-off-by: danfengl <danfengl@vmware.com>

The errors of restore/backup may be stored in object storage
The well formatted output of describe is also helpful for debugging.
This commit add the command to the crashd script so the output of
"velero backup/restore describe xxx" can be collected
Signed-off-by: Daniel Jiang <jiangd@vmware.com>

Recovery the workround for aws pending issue

Signed-off-by: danfengl <danfengl@vmware.com>

Use velero debug command to dump the logs when case failed

Signed-off-by: Wenkai Yin(尹文开) <yinw@vmware.com>

Fix the link and content for upgrade instruction

Signed-off-by: Daniel Jiang <jiangd@vmware.com>

Generate docs and changelog for v1.7

Signed-off-by: Bridget McErlean <bmcerlean@vmware.com>

Add upgrade test into E2E tests

Signed-off-by: danfengl <danfengl@vmware.com>

Signed-off-by: Bridget McErlean <bmcerlean@vmware.com>

Signed-off-by: Bridget McErlean <bmcerlean@vmware.com>

Add `velero debug` to documentation

This commits updates the `troubleshooting` section in the doc to ask
users to collect log via `velero debug`.
Signed-off-by: Daniel Jiang <jiangd@vmware.com>

* Add namespace validation in the client
Signed-off-by: F. Gold <fgold@vmware.com>

* Add namespace validation in the backup controller
Signed-off-by: F. Gold <fgold@vmware.com>

* Add changelog for PR 4057
Signed-off-by: F. Gold <fgold@vmware.com>

* Update Copyright notice
Signed-off-by: F. Gold <fgold@vmware.com>

* Update include_excludes_test.go to follow Go standards and be easier to read
Signed-off-by: F. Gold <fgold@vmware.com>

* Add unit tests for namespace validation functions
Signed-off-by: F. Gold <fgold@vmware.com>

* Make changes per review comments

- use one set of namespace validation logic instead of writing two
- remove duplicate namespace validation functions and tests
- add namespace validation tests in includes_excludes_test.go
Signed-off-by: F. Gold <fgold@vmware.com>

* Return all ns validation err msgs as error list
Signed-off-by: F. Gold <fgold@vmware.com>

* Make error message more clear
Signed-off-by: F. Gold <fgold@vmware.com>

More details please refer to #4098

Fixes #4098
Signed-off-by: Wenkai Yin(尹文开) <yinw@vmware.com>

Distinguish between different unnamed node ports when preserving

pass velero cli executable to crashd

This commit fixes the issue when velero CLI is not in `PATH` or compiled
to other file names.
Signed-off-by: Daniel Jiang <jiangd@vmware.com>

Velero was including DownwardAPI volumes when backing up with restic.
When restoring these volumes, it triggered a known issue with restic (as
seen in #3863). Like projected volumes, these volumes should be skipped
as their contents are populated by the Kubernetes API server.

With this change, we are now skipping the restic backup of volumes with
a DownwardAPI source. We are also skipping the restore of any volume
that had a DownwardAPI source as there will exist backups that were
taken prior to this fix being introduced. This will allow these backups
to be restored succesfully.
Signed-off-by: Bridget McErlean <bmcerlean@vmware.com>

This commit removes `IsUnstructuredCRDReady` since
kubernetes/kubernetes#87675 is fixed.
Is uses `Is1CRDReady` to check the readiness of CRD.

After v1.7 we may consider merge the funcx `IsV1Beta1CRDReady` and
`IsV1CRDReady`
Signed-off-by: Daniel Jiang <jiangd@vmware.com>

Enhance e2e test

1. Support to customize the restic restore helper image
2. Use a seperated context when doing the clean up works
3. Wait a while before doing the the restore for aws to avoid #1799
Signed-off-by: Wenkai Yin(尹文开) <yinw@vmware.com>

1. Check the error when waiting for restice daemonset to be ready, so
   the timeout will be reported
2. Add support for gcp provider and fail early if the provider is
   unknown
Signed-off-by: Daniel Jiang <jiangd@vmware.com>

This PR added a subcommand `velero debug`, which leverages `crashd` to
collect logs and specs of velero server components and bundle them in a
tarball.
Signed-off-by: Daniel Jiang <jiangd@vmware.com>

fixes for CVE-2021-3121 and CVE-2021-3580

Install/uninstall velero by CLI in the E2E test case

Do this for two reasons:
1. Verify the functionalities for installation and uninstllation of CLI
2. We want to add upgrade test case which needs to install different versions of velero, calling libraries is impossible for this

fixes #4062
Signed-off-by: Wenkai Yin(尹文开) <yinw@vmware.com>

Signed-off-by: jacklu1024 <jacklu1024@outlook.com>

Signed-off-by: kahirokunn <okinakahiro@gmail.com>

Signed-off-by: kahirokunn <okinakahiro@gmail.com>

Signed-off-by: Eleanor Millman <emillman@vmware.com>

Change the base image to distroless
Signed-off-by: Wenkai Yin(尹文开) <yinw@vmware.com>

Signed-off-by: Lars Lehtonen <lars.lehtonen@gmail.com>

* Add document for TLS error 116

When using a custom S3 compatible server, backups/restore may fail with
TLS error 116. This happens because the S3 server expects Velero to
send client certificate during SSL TLS v1.3 handshake.
You will need to modify your S3 server settings to turn off client
certificate authentication.
Signed-off-by: Himanshu Mehra <himanshu.mehra91@gmail.com>

* Add document for TLS error 116

When using a custom S3 compatible server, backups/restore may fail with
TLS error 116. This happens because the S3 server expects Velero to
send client certificate during SSL TLS v1.3 handshake.
You will need to modify your S3 server settings to turn off client
certificate authentication.
Signed-off-by: Himanshu Mehra <himanshu.mehra91@gmail.com>

* Address comments from reviewers
Signed-off-by: Himanshu Mehra <himanshu.mehra91@gmail.com>