[ci:component:github.com/gardener/etcd-backup-restore:v0.37.0->v0.38.0]

[gardener-github-actions]

Release Notes:

[github.com/gardener/etcd-backup-restore:v0.38.0]

📰 Noteworthy

• [OPERATOR] etcd-backup-restore now supports worm immutable objects for storage provider: ALI Cloud OSS, provided by the WORM Lock feature. by @ishan16696 [#887]
• [OPERATOR] Support for WORM lock (ALI Cloud's OSS) in etcd-backup-restore is backward compatible. For more info please refer to this doc: https://github.com/gardener/etcd-backup-restore/blob/master/docs/usage/enabling_immutable_snapshots.md by @ishan16696 [#887]
• [OPERATOR] Snapshots garbage collection performed by etcd-backup-restore (if enabled) for ALI Cloud OSS is performed only when the snapshots's retention period get expires. by @ishan16696 [#887]

✨ New Features

• [OPERATOR] S3 snapstore now support web identity authentication.
  To be enabled, the roleARN and token credentials files or json fields must be set, while accessKeyID and secretAccessKey has to be unset. by @vpnachev [#892]

🐛 Bug Fixes

• [OPERATOR] The copy command does not attempt to upload snapshots with the .final suffix in the source to the destination store if they are already in the destination. by @renormalize [#907]

🏃 Others

• [DEVELOPER] Convert .reuse/dep5 to REUSE.toml. by @shreyas-s-rao [#904]
• [OPERATOR] The container base image has been updated to debian12. by @vpnachev [#892]

BoM Diff

Added components: 0
Changed components: 1
Removed components: 0

Changed Components:

⚙ github.com/gardener/etcd-backup-restore: v0.37.0 → v0.38.0

Component Details:

⚙ github.com/gardener/etcd-backup-restore:v0.37.0 → v0.38.0

Resource	Version Change
➕ release-notes-archive	v0.38.0
🔄 etcdbrctl	v0.37.0 → v0.38.0
🔄 check-build-step-log	v0.37.0 → v0.38.0
🔄 release-notes	v0.37.0 → v0.38.0

[gardener-prow]

Hi @gardener-github-actions[bot]. Thanks for your PR.

I'm waiting for a gardener member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[gardener-robot-ci-1]

Thank you @gardener-github-actions[bot] for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.

[shreyas-s-rao]

/ok-to-test

[ishan16696]

/test pull-etcd-druid-e2e-kind

[ishan16696]

/test pull-etcd-druid-e2e-kind

[ishan16696]

Flaky tests

Summarizing 1 Failure:
  [FAIL] Etcd Single-node etcd configuration Scaling up from single-node to multi-node without TLS [It] should scale a single-node etcd (TLS not enabled for peerUrl) to a multi-node etcd cluster (TLS not enabled for peerUrl)
  /home/prow/go/src/github.com/gardener/etcd-druid/test/e2e/etcd_multi_node_test.go:148
Ran 8 of 8 Specs in 1200.099 seconds
FAIL! -- 7 Passed | 1 Failed | 0 Pending | 0 Skipped

/test pull-etcd-druid-e2e-kind

[shreyas-s-rao]

/lgtm