Scott Seago

Results 19 issues of Scott Seago

This design combines the requirements for the previously-merged Upload Progress Monitoring design with the requirements for the (not submitted but discussed in meetings and slack) proposed asynchronous item action plugins...

Area/Design
kind/changelog-not-required

This is analogous to the BSL creds work that was done previously, but for VSLs instead. Originally the per-BSL credentials support was intended to be added to VolumeSnapshotLocations as well....

has-unit-tests
has-changelog

**Describe the problem/challenge you have** the RestoreItemAction plugin interface needs a method to query the plugin as to whether the returned additionalItems are created and ready (since for some controllers,...

**Describe the problem/challenge you have** Originally the per-BSL credentials support was intended to be added to VolumeSnapshotLocations as well. Some initial work was already done for this but was reverted...

1.10-candidate

This includes necessary changes to support async item action monitoring. This includes the design for the BackupItemAction v2 API which is to be implemented in the Velero 1.11 dev cycle....

Area/Design
kind/changelog-not-required

This provides a test implementation of a v2 BackupItemAction plugin. It is fully functional (built on top of https://github.com/vmware-tanzu/velero/pull/5271), but the added interface method is for testing purposes only. This...

has-unit-tests

Signed-off-by: Scott Seago Thank you for contributing to Velero! This includes necessary changes to support async item action monitoring. This includes the design for the VolumeSnapshotter v2 API which is...

Area/Design
kind/changelog-not-required

Signed-off-by: Scott Seago This includes necessary changes to support async item action monitoring as well as the Wait for Additional Items feature. This includes the design for the RestoreItemAction v2...

Area/Design
kind/changelog-not-required

**What steps did you take and what happened:** A second restic restore into a volume should update the volume to match the backup. There's a bug in current restic releases...

Restic
backlog

**What steps did you take and what happened:** In a cluster with node autoscaling enabled, creating a datamover backup with a bunch of volumes may trigger new node creation to...

Needs triage