Invalid path in BackupRepository

[nobleess]

What steps did you take and what happened:

run this

# Standard Kubernetes API Version declaration. Required.
apiVersion: velero.io/v1
# Standard Kubernetes Kind declaration. Required.
kind: Backup
# Standard Kubernetes metadata. Required.
metadata:
  # Backup name. May be any valid Kubernetes object name. Required.
  name: test
  # Backup namespace. Must be the namespace of the Velero server. Required.
  namespace: velero
# Parameters about the backup. Required.
spec:
  itemOperationTimeout: 6h
  includedNamespaces:
  - 'cnpg'
  includedResources:
    - pod
  snapshotVolumes: false              
  defaultVolumesToFsBackup: true 
  storageLocation: default
  ttl: 24h0m0s

i have

apiVersion: velero.io/v1
kind: BackupRepository
metadata:
  creationTimestamp: "2025-03-28T09:39:57Z"
  generateName: cnpg-default-kopia-
  generation: 3
  labels:
    velero.io/repository-type: kopia
    velero.io/storage-location: default
    velero.io/volume-namespace: cnpg
  name: cnpg-default-kopia-69vrk
  namespace: velero
  resourceVersion: "1676870"
  uid: 5170ed7a-7126-4019-91a1-be53176e0b57
spec:
  backupStorageLocation: default
  maintenanceFrequency: 1h0m0s
  repositoryType: kopia
  resticIdentifier: s3:https://aws/testing-backup/media/restic/cnpg
  volumeNamespace: cnpg
status:
  lastMaintenanceTime: "2025-03-28T09:39:59Z"
  phase: Ready

What did you expect to happen:

apiVersion: velero.io/v1
kind: BackupRepository
metadata:
  creationTimestamp: "2025-03-28T09:39:57Z"
  generateName: cnpg-default-kopia-
  generation: 3
  labels:
    velero.io/repository-type: kopia
    velero.io/storage-location: default
    velero.io/volume-namespace: cnpg
  name: cnpg-default-kopia-69vrk
  namespace: velero
  resourceVersion: "1676870"
  uid: 5170ed7a-7126-4019-91a1-be53176e0b57
spec:
  backupStorageLocation: default
  maintenanceFrequency: 1h0m0s
  repositoryType: kopia
*  resticIdentifier: s3:https://aws/testing-backup/media/kopia/cnpg *
  volumeNamespace: cnpg
status:
  lastMaintenanceTime: "2025-03-28T09:39:59Z"
  phase: Ready

how i check
dont work
kopia repository connect s3 --bucket=testing-backup --access-key= --secret-access-key=--endpoint=aws --prefix=media/restic/cnpg/
but
kopia repository connect s3 --bucket=testing-backup --access-key= --secret-access-key=--endpoint=aws --prefix=media/kopia/cnpg/
work

Environment:

• Velero version (use velero version):
  Client:
  Version: v1.15.2
  Git commit: -
  Server:
  Version: v1.15.2
• Velero features (use velero client config get features):
• Kubernetes version (use kubectl version):
  velero client config get features
  features:
• Kubernetes installer & version:
  v1.32.2
• Cloud provider or hardware configuration:
  s3
• 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 "I would like to see this bug fixed as soon as possible"
• 👎 for "There are more important bugs to focus on right now"

[kaovilai]

This is expected.. it's called resticIdentifier and is only used by restic path if exists. When you use kopia, the text populated there is unused. We will probably remove to reduce confusion when restic backup is no longer restorable from velero..

[weshayutin]

@reasonerjt @sseago any chance we fix this in a 1.16.x release? Just a little embarrassing issue that may give users a bad impression imho.

[sseago]

Kopia doesn't need this field, so if we decided to make a change here, it would be to leave it empty if repositoryType is "kopia".