S3 bucket versioning
jorge07 opened this issue · 4 comments
Single node ETCD clusters are sometimes useful for things like temporary clusters or small staging clusters. We got an issue today with the upgrade from 0.12.x to 0.13.x in one of our staging clusters and while debugging the issue and started the ETCD manually (without etcdadm) our snapshot in S3 was overwritten for a brand new snaptshot.db file. Causing the rollback to fail too and entering in an invalid, non recoverable state.
Suggestions:
- Request S3 versioning
- Update documentation and expand a bit the workflows about ETCD management
- Both
Happy to help with whatever you think is better here.
And as always thanks for the amazing job.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
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/test-infra repository.