Skip to content

Add the ability to use a custom pvc transfer image for source and destination #57

Description

@jmontleon

For downstream we will likely need to use allow using a different rsync-transfer image. Even with a community release it will be necessary in disconnected or restricted networks. We'll need to update the pvc-transfer ClusterTask to accept these options.

Once those PRs are merged and we've decided how to pass them in we should update the ClusterTask to deal with them properly.

Based on current PRs it should look roughly like so:

crane transfer-pvc \
          --source-image=quay.io/jmontleon/rsync-source-transfer:latest \
          --destination-image=quay.io/jmontleon/rsync-transfer:latest \
...

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.priority/normalHigher priority than priority/minor. Nice to have.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions