🎉Velero 1.13 is OUT! 🎉

[Orlin Vasilev]

Hello Community,

Super happy to inform you that Velero 1.13 is out and you can find all the details in the release notes here:

https://github.com/vmware-tanzu/velero/releases/tag/v1.13.0

Here are some highlights:

Resource Modifier Enhancement

Node-Agent Concurrency

Parallel Files Upload Options
Write Sparse Files Options
Backup Describe
Backup's new VolumeInfo metadata
....

Please test and upgrade at your convenience and report any issues if you hit any :)

Thank you!

Orlix

Velero Community Manager

[spesys services]

Hi,
This is the first time I've given feedback on a product...

I installed the latest version 1.13.1 of velero on minikube version 1.32.0 for testing before installing it on my own kubernetes servers.

I have two problems:
one on the network port when I launch it it tells me:

FAILED: no Service with the name "velero" found

when i check i found:

kubectl get svc -n velero
NAME     TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
velero   ClusterIP   10.102.245.221   <none>        8085/TCP   10s

for solve that i put into my file values.yaml

service:
  name: velero
  type: NodePort
  port: 80
  targetPort: 8085
  protocol: TCP

I must execute an other install to by pass this mistake

and one  on activating the gcp plugin. I followed the values.yaml file to make my own and on initcontainer,

This module never installs the plugin.

kubectl logs -n velero velero-76b68df7f8-2cs54

time="2024-04-04T09:33:49Z" level=error msg="Current BackupStorageLocations available/unavailable/unknown: 0/1/0, BackupStorageLocation \"default\" is unavailable: unable to locate ObjectStore plugin named velero.io/gcp)" controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:178"

my configuration into values.yaml file is: (like your default values;yaml file) 

image:
  repository: velero/velero
  tag: v1.13.1
  pullPolicy: IfNotPresent

initContainers:
  - name: velero-velero-plugin-for-gcp
    image: velero/velero-plugin-for-gcp:v1.9.0
    imagePullPolicy: always
    volumeMounts:
      - mountPath: /target
        name: plugins

volumes:
  - name: plugins
    emptyDir: {}

  - name: cloud-credentials
    secret:
      secretName: credentials

if you want more explanation on my configuration or logs, I can send them to you

thanking you in advance for your help
Sincerely
Frank A.