[github.com/gardener/etcd-backup-restore:v0.45.1]
🐛 Bug Fixes
[OPERATOR]etcd-backup-restorenow re-reads the etcd cluster size on every initialization instead of only at process startup for multi-node cluster, so a member whose data directory is corrupted after a scale-out rejoins the existing cluster as a learner instead of restoring from a backup snapshot and bootstrapping a new single-member cluster. by @seshachalam-yv [#1080]
application/spdx+json
- etcdbrctl-sbom-ref:
europe-docker.pkg.dev/gardener-project/releases/gardener/etcdbrctl@sha256:9e51b77e167d53d0db008ccf990fc0cee0f4d1f296e8866813343acda13b058c - etcdbrctl-sbom-ref:
europe-docker.pkg.dev/gardener-project/releases/gardener/etcdbrctl@sha256:9f32c62a4e469281b55449bb3d4af5f93c950f77b895c44182509e0f419a0f1e
application/vnd.cyclonedx+json
- etcdbrctl-sbom-ref:
europe-docker.pkg.dev/gardener-project/releases/gardener/etcdbrctl@sha256:8aba3af156e871a23d9a70a2243f786b745335e89053f2fae93a3ad5479f43d6 - etcdbrctl-sbom-ref:
europe-docker.pkg.dev/gardener-project/releases/gardener/etcdbrctl@sha256:af02fe2e6ae8776bfa30a3d2cdf22603af38d88d13994a0aab5f12f1301701fb
Container (OCI) Images
- etcdbrctl:
europe-docker.pkg.dev/gardener-project/releases/gardener/etcdbrctl:v0.45.1