Ensure default bucket gets re-created when fake-aws-s3 pod dies

Open
#90 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
helm, kubernetes
Domain
devops, infrastructure

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.

Description

Reliability

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

Ref.:
https://github.com/helm/charts/blob/master/stable/minio/templates/post-install-create-bucket-job.yaml

https://github.com/wireapp/wire-server-deploy/blob/master/charts/fake-aws-s3/values.yaml#L8-L11

Dominant language
Shell
Stars
113
Forks
44
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wireapp/wire-server-deploy

All issues in wireapp/wire-server-deploy

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.