What steps did you take and what happened:
I upgraded to velero-plugin-for-aws 0.14.2. Afterwards my backupStorageLocations are in unavailable state because no Region is configured.
config:
checksumAlgorithm: ""
insecureSkipTLSVerify: "true"
s3ForcePathStyle: "true"
s3Url: http://localhost:8088
status:
lastSyncedTime: "2026-07-06T09:02:41Z"
lastValidationTime: "2026-07-06T09:02:43Z"
message: 'BackupStorageLocation "rclone-s3" is unavailable: rpc error: code =
Unknown desc = operation error S3: ListObjectsV2, failed to resolve service
endpoint, endpoint rule error, A region must be set when sending requests to
S3.'
If I set the region to any string e.g. region: "dummy" the backupStorageLocation is available again.
What did you expect to happen:
I would expect that 'breaking changes' are announced in the release notes.
Anything else you would like to add:
Is it a valid solution to use a "dummy" value or does this impose other issues e.g. while restoring from backup?
Environment:
- Velero version (use
velero version): v1.18.2
- Velero features (use
velero client config get features):
- Kubernetes version (use
kubectl version): Server Version: v1.35.6
- Kubernetes installer & version: kubeadm
- Cloud provider or hardware configuration: openstack
- OS (e.g. from
/etc/os-release): flatcar 4593.2.3
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"
What steps did you take and what happened:
I upgraded to velero-plugin-for-aws 0.14.2. Afterwards my backupStorageLocations are in unavailable state because no Region is configured.
If I set the region to any string e.g.
region: "dummy"the backupStorageLocation is available again.What did you expect to happen:
I would expect that 'breaking changes' are announced in the release notes.
Anything else you would like to add:
Is it a valid solution to use a "dummy" value or does this impose other issues e.g. while restoring from backup?
Environment:
velero version): v1.18.2velero client config get features):kubectl version): Server Version: v1.35.6/etc/os-release): flatcar 4593.2.3Vote 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.