-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
Incidents & Support
-
3
-
False
-
-
False
-
ToDo
-
-
-
Critical
-
Very Likely
-
0
-
Customer Facing
-
10
-
None
-
Unset
-
Unknown
-
None
Description of problem:
We have an issue where a customer sets some labels on a namespace and uses validating webhooks to force the label being set when a namespace is created, manually or through a restore operation.
If you backup any resources created in this namespace, the actual namespace resource is not backed up. So when the restore is executed and the namespace doesn't exist, the restore operation creates a namespace using the resource metadata.namespace name. But since the namespace was not backed up , any other information is missing from the new ns resource and the validating webhooks fails the ns creation because is missing the required label.
We request that the namespace resource is also backed up with the resource so that it can be fully recreated on restore, if it doesn't exist.
Version-Release number of selected component (if applicable):
OADP 1.4.4
How reproducible:
Always
Steps to Reproduce:
1. Create a namespace and set a label label1: value; define a validating webhooks that fails a ns creation if the ns doesn't have the label1
2. Create a resource under that ns
3. Back up the resource using a Velero backup
4. Delete the ns
5. Run the Restore operation to recreate the resource.
Actual results:
The ns is created by restore but with no label. And since the validating webhooks doesn't allow for the ns to be created, the restore fails
Expected results:
Step 5 should successfully recreate the backed up resource
Additional info: