-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
Not Selected
-
ToDo
-
-
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
None
This issue tracks the upstream Velero GitHub issue #7904 which is part of the Velero v1.18 milestone.
Description
The Changing PVC selected-node feature is not required and not working well, so we need to deprecate it. Details as below:
-
- It is not required — the feature was used to fix a limitation of old Kubernetes versions, but since Kubernetes 1.16, the limitation has been fixed
2. It conflicts with the principle of WaitForFirstConsumer, so it doesn't work with WaitForFirstConsumer mode volume
3. From the description here, the volume.kubernetes.io/selected-node annotation is an output of the scheduler, so changing it is more like a hack
- It is not required — the feature was used to fix a limitation of old Kubernetes versions, but since Kubernetes 1.16, the limitation has been fixed
Upstream Details
- GitHub Issue: https://github.com/vmware-tanzu/velero/issues/7904
- Status: Open
- Assignee: Lyndon-Li
- Labels: Breaking change, doc-change-required, feature-deprecation
- Created: 2024-06-19T02:19:01Z
- Updated: 2025-09-01T02:48:57Z
This is a breaking change that requires documentation updates as part of deprecating an existing feature.