Merge pull request vmware-tanzu#3971 from zubron/release-1.6.2

Add cherry-pick commits and changelog for v1.6.2

Merge pull request vmware-tanzu#3889 from zubron/release-1.6.1

Add cherry-pick commits and changelog for v1.6.1

Merge pull request vmware-tanzu#3673 from zubron/release-1.6-changelo…

…g-docs

Add changelog and docs for v1.6.0

 Upgrade docs for v1.6.0-rc2 (vmware-tanzu#3662)

* Update changelog for v1.6.0-rc.2

Signed-off-by: Carlisia <[email protected]>

* Update docs for v1.6.0-rc.2

Signed-off-by: Carlisia <[email protected]>

* Upgrade docs for v1.6.0-rc2

Signed-off-by: Carlisia <[email protected]>

Add cherry-pick commits and changelog for v1.5.4 (vmware-tanzu#3651)

* Restore CAPI cluster objects in a better order

Restoring CAPI workload clusters without this ordering caused the
capi-controller-manager code to panic, resulting in an unhealthy cluster
state.

This can be worked around
(https://community.pivotal.io/s/article/5000e00001pJyN41611954332537?language=en_US),
but we provide the inclusion of these resources as a default in order to
provide a better out-of-the-box experience.

Signed-off-by: Nolan Brubaker <[email protected]>

* Add changelog

Signed-off-by: Nolan Brubaker <[email protected]>

* Use pod namespace from backup when matching PVBs (vmware-tanzu#3475)

* Use pod namespace from backup when matching PVBs

In vmware-tanzu#3051, we introduced an additional check to ensure that a PVB matched
a particular pod by checking both the name and the namespace of the pod.
This caused an issue when using a namespace mapping on restore. In the
case where a namespace mapping is being used, the check for whether a
PVB matches a particular pod will fail as the PVB was created for the
original pod namespace and is not aware of the new namespace mapping
being used. This resulted in PVRs not being created for pods that were
being restored into new namespaces. The restic init containers were
being created to wait on the volume restore, however this would cause
the restored pods to block indefinitely as they would be waiting for a
volume restore that was not scheduled.

To fix this, we use the original namespace of the pod from the backup to
match the PVB to the pod being restored, not the new namespace where
the pod is being restored into.

Fixes vmware-tanzu#3467.

Signed-off-by: Bridget McErlean <[email protected]>

* Explain why the namespace mapping can't be used

Signed-off-by: Bridget McErlean <[email protected]>

* Allow Dockerfiles to be configurable (vmware-tanzu#3634)

For internal builds of Velero, we need to be able to specify an
alternative Dockerfile which uses an alternative image registry to pull
the base images from. This change adapts our Makefile such that both the
main Dockerfile and build image Dockerfile can be overridden.

We have some special handling for the build image to only build when the
Dockerfile has changed. In this case, we check whether a custom
Dockerfile has been provided, and always rebuild in that case. For
custom build image Dockerfiles, use a fixed tag rather than the one
based on commit SHA of the original file.

Signed-off-by: Bridget McErlean <[email protected]>

* Combine CRD install verification into 1 job, and update k8s versions (vmware-tanzu#3448)

* Validate CRDs against latest Kubernetes versions

Add Kubernetes v1.19 and v1.20 series images, and consolidate the job
into a single file to reduce repetition.

Signed-off-by: Nolan Brubaker <[email protected]>

* Ignore job if the changes are only site/design

Signed-off-by: Nolan Brubaker <[email protected]>

* Fix codespell error

Signed-off-by: Nolan Brubaker <[email protected]>

* Cache Velero binary for reuse on workers

This will cache the Velero binary based on the PR number and a SHA256 of
the generated binary.

This way, the runners testing each version of Kubernetes do not need to
build it independently.

Signed-off-by: Nolan Brubaker <[email protected]>

* Fix GitHub event access

Signed-off-by: Nolan Brubaker <[email protected]>

* Wrap output path in quotes

Signed-off-by: Nolan Brubaker <[email protected]>

* Move code checkout to build step

Signed-off-by: Nolan Brubaker <[email protected]>

* Also cache go modules

Signed-off-by: Nolan Brubaker <[email protected]>

* Fix syntax issues

Signed-off-by: Nolan Brubaker <[email protected]>

* Download cached binary on each node

Signed-off-by: Nolan Brubaker <[email protected]>

* Use cached go modules on main CI

Signed-off-by: Nolan Brubaker <[email protected]>

* Add changelog for v1.5.4

Signed-off-by: Bridget McErlean <[email protected]>

Co-authored-by: Nolan Brubaker <[email protected]>

Merge pull request vmware-tanzu#3637 from zubron/release-1.6-rc1

Add changelog and docs for v1.6.0-rc.1

Add changelog for v1.5.3

Signed-off-by: Bridget McErlean <[email protected]>

v1.4.3 cherry-picks and changelogs (vmware-tanzu#3025)

* Ensure PVs and PVCs remain bound when doing a restore (vmware-tanzu#3007)

* Only remove the UID from a PV's claimRef

The UID is the only part of a claimRef that might prevent it from being
rebound correctly on a restore. The namespace and name within the
claimRef should be preserved in order to ensure that the PV is claimed
by the correct PVC on restore.

Signed-off-by: Nolan Brubaker <[email protected]>

* Remap PVs claimRef.namespace on relevant restores

When remapping namespaces, any included PVs need to have their claimRef
updated to point remapped namespaces to the new namespace name in order
to be bound to the correct PVC.

Signed-off-by: Nolan Brubaker <[email protected]>

* Update tests and ensure claimRef namespace remaps

Signed-off-by: Nolan Brubaker <[email protected]>

* Remove lowercased uid field from unstructured PV

Signed-off-by: Nolan Brubaker <[email protected]>

* Fix issues that prevented PVs from being restored

Signed-off-by: Nolan Brubaker <[email protected]>

* Add changelog

Signed-off-by: Nolan Brubaker <[email protected]>

* Dynamically reprovision volumes without snapshots

Signed-off-by: Nolan Brubaker <[email protected]>

* Update test for lower case uid field

Signed-off-by: Nolan Brubaker <[email protected]>

* Remove stray debugging print statement

Signed-off-by: Nolan Brubaker <[email protected]>

* Fix typo, remove extra code, add tests.

Signed-off-by: Nolan Brubaker <[email protected]>

* fix: rename the PV if VolumeSnapshotter has modified the PV name (vmware-tanzu#2835)

When VolumeSnapshotter sets the PV name via SetVolumeID and PV is
not there in the cluster, velero does not rename the PV. Which causes
the pvc to be in the lost state as pvc points to the old PV but pv object
has been renamed by VolumeSnapshotter.

Signed-off-by: Pawan <[email protected]>

* adding a test case for pv rename

Signed-off-by: Pawan <[email protected]>
Signed-off-by: Nolan Brubaker <[email protected]>

* restore proper lowercase/plural CRD resource (vmware-tanzu#2949)

* restore proper lowercase/plural CRD resource

This commit restores the proper resource string
"customresourcedefinitions" for CRD. The prior change to
"CustomResourceDefinition" was made because this was being used
in another place to populate the CRD "Kind" field in
remap_crd_version_action.go -- there, just use the correct Kind
string instead of pulling from Resource.

Signed-off-by: Scott Seago <[email protected]>

* add changelog

Signed-off-by: Scott Seago <[email protected]>

* Update changelogs for v1.4.3

Signed-off-by: Nolan Brubaker <[email protected]>

Co-authored-by: Pawan Prakash Sharma <[email protected]>
Co-authored-by: Scott Seago <[email protected]>

Add changelog and docs for v1.5 release (vmware-tanzu#2941)

* Add changelog and docs for v1.5 release

Signed-off-by: Nolan Brubaker <[email protected]>

* Fix markdown indentation

Signed-off-by: Nolan Brubaker <[email protected]>

* Fix URLs with patch version

Signed-off-by: Nolan Brubaker <[email protected]>

* Fix example link

Signed-off-by: Nolan Brubaker <[email protected]>