Backup resource status URL doesn't match configuration.

[millasml]

What happened?

If a new backup resource is created while an existing backup is still running, the updateBackupStatus reconciler will execute this logic:
update_backup_status.go#L108-L118.

At this point, the backup status is updated to use the URL from the currently running (previous) backup.

After this, there are no further checks to ensure that the backup URLs match. The reconciler simply sees that a backup is running, assumes everything is correct, and reports that the backup is reconciled—even if the URLs differ.

The code is also not suited for having more than one backup resource.

What did you expect to happen?

The existing backup should be modified to match that of the backup resource.

How can we reproduce it (as minimally and precisely as possible)?

Create a backup resource while a backup is running.

Anything else we need to know?

No response

FDB Kubernetes operator

$ kubectl fdb version
2.9.0

Kubernetes version

$ kubectl version
Client Version: v1.32.2
Kustomize Version: v5.5.0
Server Version: v1.31.1101

Cloud provider

aws