Skip to content

Conversation

@MaloLelandais
Copy link

Thank you for contributing to Velero!

Please add a summary of your change

Does your change fix a particular issue?

Fixes #(issue)

Please indicate you've done the following:

ywk253100 and others added 30 commits July 25, 2025 14:44
Bug fix: increase the WaitGroup counter before start the goroutine

Signed-off-by: Wenkai Yin(尹文开) <[email protected]>
Signed-off-by: Lyndon-Li <[email protected]>
Clear validation errors when schedule is valid

Fixes vmware-tanzu#8571

Signed-off-by: Wenkai Yin(尹文开) <[email protected]>
Merge restore helper image into Velero server image

Fixes vmware-tanzu#8484

Signed-off-by: Wenkai Yin(尹文开) <[email protected]>
This commit makes change in restore finalizer controller, to make it
check the status in item operation of a PVC before patch the PV that is
bound to it.  If the operation is not successful it will skip patching
the PV.

Signed-off-by: Daniel Jiang <[email protected]>
Signed-off-by: Lyndon-Li <[email protected]>
Signed-off-by: Matthieu MOREL <[email protected]>
Signed-off-by: Matthieu MOREL <[email protected]>
Signed-off-by: Matthieu MOREL <[email protected]>
…server to avoid API server issue

Check the PVB status via podvolume Backupper rather than calling API server to avoid API server issue

Fixes vmware-tanzu#8587

Signed-off-by: Wenkai Yin(尹文开) <[email protected]>
Lyndon-Li and others added 27 commits July 28, 2025 14:42
Signed-off-by: Matthieu MOREL <[email protected]>
…-tanzu#9063)

* Add support for image registry proxy in Kibishii installation
Signed-off-by: Priyansh Choudhary <[email protected]>
* issue 8344: constrain data path exposure.

Signed-off-by: Lyndon-Li <[email protected]>
…anzu#8880)

This PR fixes issue vmware-tanzu#8870 where Velero was unnecessarily adding the restore-wait init container when restoring pods with volumes that were backed up using native datamover or CSI.

When restoring pods with volumes, Velero was always adding the restore-wait init container, even when the volumes were backed up using native datamover or CSI and didn't need file system restores. This was causing unnecessary overhead and potential issues.

PVR action to remove restore-wait init container on restore

Changes:
- Remove ALL existing restore-wait init containers before deciding whether to add a new one
- This covers both scenarios: when no file system restore is needed AND when preventing duplicates
- Simplify the add logic since we've already cleaned up existing containers
- Add better logging to show how many containers were removed

Signed-off-by: Tiger Kaovilai <[email protected]>
…e-tanzu#9076)

issue 9053: remove selected-node annotation during PVC restore

Signed-off-by: Lyndon-Li <[email protected]>
…factor credential retrieval

Signed-off-by: Priyansh Choudhary <[email protected]>
* Refactor backup volume info retrieval and snapshot checkpoint building in e2e tests
Signed-off-by: Priyansh Choudhary <[email protected]>

log backup volume info retrieval and snapshot checkpoint building
Signed-off-by: Priyansh Choudhary <[email protected]>

Add error handling for volume info retrieval in backup tests
Signed-off-by: Priyansh Choudhary <[email protected]>

Add error handling for volume info retrieval in backup tests
Signed-off-by: Priyansh Choudhary <[email protected]>

* Update snapshot checkpoint building to use DefaultKibishiiWorkerCounts
Signed-off-by: Priyansh Choudhary <[email protected]>

---------

Signed-off-by: Priyansh Choudhary <[email protected]>
Signed-off-by: Shubham Pampattiwar <[email protected]>

Add changelog file

Signed-off-by: Shubham Pampattiwar <[email protected]>

make update

Signed-off-by: Shubham Pampattiwar <[email protected]>

lint fix

Signed-off-by: Shubham Pampattiwar <[email protected]>

add unit tests for getVSForPVC func

Signed-off-by: Shubham Pampattiwar <[email protected]>

Use v1beta1 instead of v1 v1alpha1

Signed-off-by: Shubham Pampattiwar <[email protected]>

go mod tidy

Signed-off-by: Shubham Pampattiwar <[email protected]>

update updateVGSCreatedVS func to use retry on conflict

Signed-off-by: Shubham Pampattiwar <[email protected]>

make update minor fix

Signed-off-by: Shubham Pampattiwar <[email protected]>

fix ut assert

Signed-off-by: Shubham Pampattiwar <[email protected]>

Address PR feedback

Signed-off-by: Shubham Pampattiwar <[email protected]>

minor updates

Signed-off-by: Shubham Pampattiwar <[email protected]>

remove unsused func and add todo for dep upgrades

Signed-off-by: Shubham Pampattiwar <[email protected]>
vmware-tanzu#9074)

Enable parameterized kubelet mount path during node-agent installation

Signed-off-by: longyuxiang <[email protected]>
Signed-off-by: Lyndon-Li <[email protected]>
Signed-off-by: Lyndon-Li <[email protected]>
PriorityClass Support Design Proposal

Design for vmware-tanzu#8869

Signed-off-by: Tiger Kaovilai <[email protected]>
…ackup cmd (vmware-tanzu#9056)

add changelog file



Show defaultVolumesToFsBackup in describe only when set by the user



minor ut fix



minor fix

Signed-off-by: Shubham Pampattiwar <[email protected]>
The reason is toolchain cannot update automatically.
If 1.24 can force CI use the latest patch version,
and it will not force user to upgrade their local go version,
this should be the better approach.

Signed-off-by: Xun Jiang <[email protected]>
)

The ResticIdentifier field in BackupRepository is only relevant for restic
repositories. For kopia repositories, this field is unused and should be
omitted. This change:

- Adds omitempty tag to ResticIdentifier field in BackupRepository CRD
- Updates controller to only populate ResticIdentifier for restic repos
- Adds tests to verify behavior for both restic and kopia repository types

This ensures backward compatibility while properly handling kopia repositories
that don't require a restic-compatible identifier.

Signed-off-by: Tiger Kaovilai <[email protected]>
…hot behavior and backup method decision flow (vmware-tanzu#9091)

* Enhance File System Backup documentation with details on volume snapshot behavior and backup method decision flow

Fixes: Velero AWS snapshots not occurring with the AWS plugin vmware-tanzu#9090
Signed-off-by: Tiger Kaovilai <[email protected]>

* Clarify conditions for excluding volumes from File System Backup and enhance decision flow for volume snapshots

Signed-off-by: Tiger Kaovilai <[email protected]>

---------

Signed-off-by: Tiger Kaovilai <[email protected]>
Signed-off-by: Clément Rostagni <[email protected]>

rabse from velero remote
@clcondorcet clcondorcet force-pushed the main branch 2 times, most recently from 7ff16c5 to 1fad032 Compare July 29, 2025 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.