wireapp / wireapp/wire-server-deploy
Ensure default bucket gets re-created when fake-aws-s3 pod dies
Open
Nobody has claimed this yet.
Reliability
- Dominant language
- Shell
- Stars
- 113
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
Currently, if the pod dies, the bucket does not get recreated leading to some strange/confusing errors (such as timeouts/conn refused) that do not self heal
https://github.com/wireapp/wire-server-deploy/blob/master/charts/fake-aws-s3/values.yaml#L8-L11
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with charts/fake-aws-s3/values.yaml and compare its setup with the referenced MinIO post-install bucket-creation job template. Reproduce the failure by deleting the fake-aws-s3 pod and observe whether the default bucket returns. Done means the bucket is recreated automatically and the service recovers without timeout or connection-refused errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100