mirror of
https://github.com/vmware-tanzu/velero.git
synced 2026-09-27 10:24:57 +00:00
a9e1f5b383
* Add e2e test for namespace selection by label in resource policy Covers design step 8 of #9772: a backup with no explicit --include-namespaces (the same shape a Schedule with no includedNamespaces produces), relying entirely on a ResourcePolicy ConfigMap's includedNamespacesByLabel to select which namespaces to back up. Creates labeled and unlabeled namespaces, backs up with a ResourcePolicy ConfigMap setting includedNamespacesByLabel, and verifies only the labeled namespaces are restored - closing the e2e coverage gap #10275 deferred to velero-io/velero#10564. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com> * Add changelog entry for e2e test PR Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com> * Fix e2e test: create Backup directly, not via CLI's implicit --include-namespaces=* The kind e2e run showed every unlabeled namespace getting backed up and restored anyway. velero backup create's --include-namespaces flag defaults to ["*"] when omitted (pkg/cmd/cli/backup/create.go), so skipping the flag still sent an *explicit* wildcard - and mergeNamespacesByLabel deliberately leaves an explicit "*" untouched rather than narrowing it, so includedNamespacesByLabel never got a chance to replace anything. Create the Backup object directly via the controller-runtime client instead, leaving BackupSpec.IncludedNamespaces genuinely unset - the only way to exercise the "defaulted empty" narrowing path the CLI's own default makes unreachable. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com> --------- Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>