project-velero/kopia: ship binaries or containers for debugging

[kaovilai]

Describe the problem/challenge you have

Velero uses a fork that is not 100% bug for bug with kopia/kopia and it would be great if we could produce artifacts similarly to those found at https://github.com/kopia/kopia/releases/tag/v0.17.0 in project-velero/kopia fork.

In addition, if these binaries are added to node-agent containers (or sidecar) where it will have access to the same ENV, creds, it would be great for debugging kopia repositories without additional credential steps.

Describe the solution you'd like

Inherit/enable the same github actions of upstream and tag for every velero release that uses new fork kopia tag

Anything else you would like to add:

Could be a separate pod that inherits same env/configmaps as node agent that perhaps velero CLI launch.

Environment:

• Velero version (use velero version):
• Kubernetes version (use kubectl version):
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "The project would be better with this feature added"
• 👎 for "This feature will not enhance the project in a meaningful way"

[Lyndon-Li]

This is a rational requirement.
But we don't need to do this immediately necessarily. The current code in project-velero/kopia is still compatible with the upstream Kopia client, as long as the right version is being used.
We have clarified the base Kopia version being used by each Velero release in the release notes. So users could find the right version there and use the upstream client of that version to connect to Velero repository.

In future, along with the changes of project-velero/kopia, when we see a particular version of client is required, we will deliver it somehow.