0246a32ad0
* Use pod namespace from backup when matching PVBs In #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 #3467. Signed-off-by: Bridget McErlean <bmcerlean@vmware.com> * Explain why the namespace mapping can't be used Signed-off-by: Bridget McErlean <bmcerlean@vmware.com> |
||
|---|---|---|
| .. | ||
| unreleased | ||
| 3409-nrb | ||
| CHANGELOG-0.3.md | ||
| CHANGELOG-0.4.md | ||
| CHANGELOG-0.5.md | ||
| CHANGELOG-0.6.md | ||
| CHANGELOG-0.7.md | ||
| CHANGELOG-0.8.md | ||
| CHANGELOG-0.9.md | ||
| CHANGELOG-0.10.md | ||
| CHANGELOG-0.11.md | ||
| CHANGELOG-1.0.md | ||
| CHANGELOG-1.1.md | ||
| CHANGELOG-1.2.md | ||
| CHANGELOG-1.3.md | ||
| CHANGELOG-1.4.md | ||
| CHANGELOG-1.5.md | ||