Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Hostpath not configureable via backup secret #407

Closed
timuthy opened this issue Aug 17, 2022 · 0 comments · Fixed by #412
Closed

[BUG] Hostpath not configureable via backup secret #407

timuthy opened this issue Aug 17, 2022 · 0 comments · Fixed by #412
Labels
kind/bug Bug kind/regression Bug that hit us already in the past and that is reappearing/requires a proper solution status/closed Issue is closed (either delivered or triaged)

Comments

@timuthy
Copy link
Member

timuthy commented Aug 17, 2022

Describe the bug:
Earlier it was possible to configure the hostPath used for the local backup provider via the referenced secret in etcd.spec.backup.store.secretRef, e.g.:

apiVersion: v1
kind: Secret
metadata:
  name: etcd-backup-local
  namespace: default
stringData:
  "hostPath": "/data/etcd/backup"

Unfortunately, this is not possible anymore since the switch to the component concept with #365, it always takes /etc/gardener/local-backupbuckets as the standard path.

Expected behavior:
The hostPath to be configurable.

Environment (please complete the following information):

  • Etcd version/commit ID : v0.12.3
@timuthy timuthy added kind/bug Bug kind/regression Bug that hit us already in the past and that is reappearing/requires a proper solution labels Aug 17, 2022
@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Bug kind/regression Bug that hit us already in the past and that is reappearing/requires a proper solution status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants