7 Commits

Include renames

Author	SHA1	Message	Date
harshit sainiandGitHub	11a071637b	Use k8s.io/api well-known label constants instead of hardcoded strings (#10279) ... * refactor: use k8s.io/api well-known label constants Several well-known Kubernetes label strings were hardcoded across the codebase instead of using the constants already exported by k8s.io/api/core/v1, which is an existing dependency: "kubernetes.io/hostname" -> corev1api.LabelHostname "kubernetes.io/os" -> corev1api.LabelOSStable "topology.kubernetes.io/zone" -> corev1api.LabelTopologyZone The local kube.NodeOSLabel and zoneLabel consts, which duplicated the upstream values verbatim, are now defined in terms of the upstream constants rather than repeating the literal. Both are kept: NodeOSLabel is exported and referenced from four packages alongside NodeOSLinux and NodeOSWindows, which have no upstream equivalent, and zoneLabel sits beside the deprecated-label fallback it is compared against. No functional change - every replacement is a constant with an identical value. Signed-off-by: Harshit saini <harshitsaini1188@gmail.com> * Add changelog for #10279 Signed-off-by: Harshit saini <harshitsaini1188@gmail.com> * Cover the selected-node path in createRestorePod TestCreateRestorePod only exercised selectedNode == "", so the branch that pins the restore pod to a node was never executed. Add a case with a selected node and assert the resulting pod carries the hostname label in its node selector. Signed-off-by: Harshit saini <harshitsaini1188@gmail.com> * Also use constants for the arch and deprecated zone labels Extends the same replacement to the two remaining well-known labels raised on the issue: "kubernetes.io/arch" -> corev1api.LabelArchStable "failure-domain.beta.kubernetes.io/zone" -> corev1api.LabelFailureDomainBetaZone zoneLabelDeprecated in item_backupper.go was the last local const still repeating a literal that upstream already exports, so the zone pair now reads consistently against k8s.io/api. The deprecation note upstream applies to the label itself, not the constant; Velero reads that label deliberately as the fallback for PVs created before the topology labels existed. Signed-off-by: Harshit saini <harshitsaini1188@gmail.com> --------- Signed-off-by: Harshit saini <harshitsaini1188@gmail.com>	2026-08-17 13:37:44 +08:00
Xun Jiang	49b670a791	Replace github.com/pkg/errors by github.com/cockroachdb/errors ... Change errors.Cause to errors.Is, because github.com/cockroachdb/errors New() function create a error with error stack with depth 1, but github.com/pkg/errors's New() function create error with no depth. Signed-off-by: Xun Jiang <xun.jiang@broadcom.com>	2026-06-10 15:55:57 +08:00
Daniel JiangandGitHub	1056305ca6	Merge pull request #9565 from hollycai05/add-e2e-tests-for-PR9452 ... Add e2e test case for PR 9452	2026-04-28 14:01:26 +08:00
Xun Jiang	29a9f80f10	Compare affinity by string instead of exactly same compare. ... From 1.18.1, Velero adds some default affinity in the backup/restore pod, so we can't directly compare the whole affinity, but we can verify if the expected affinity is contained in the pod affinity. Signed-off-by: Xun Jiang <xun.jiang@broadcom.com>	2026-03-16 10:49:50 +08:00
dongqingcc	1c9c669fa0	Add e2e test case for PR 9452 ... Signed-off-by: dongqingcc <dongqingcc@vmware.com>	2026-03-06 13:38:56 +08:00
Lyndon-Li	e3b501d0d9	issue 9343: include PV topology to data mover pod affinities ... Signed-off-by: Lyndon-Li <lyonghui@vmware.com>	2026-01-23 15:45:43 +08:00
Xun Jiang	8e1c4a7dc5	Add E2E cases for node-agent-configmap. ... Fix the default BackupRepoConfig setting issue. Delete PriorityClass in migration case clean stage. Signed-off-by: Xun Jiang <xun.jiang@broadcom.com>	2025-09-02 15:03:20 +08:00