devops-42

Hi @luanphantiki thanks for your PR. I could build the container image from the Dockerfile and have created a deployment configuration for a k8s cluster. Vault is configured with an...

@luanphantiki Thanks for clarification, I changed the address to the internal `svc` address of the leading pod (have a cluster of 3 pods deployed). Now the snapshot provider tries to...

My bad, when cleaning up the config file I accidentally deleted the `"` Concerning the `curl` call: I got a 307 status code: ``` HTTP/1.1 307 Temporary Redirect Cache-Control: no-store...

@luanphantiki I do use Raft as storage, here's a redacted output of the `vault status` command ``` Key Value --- ----- Seal Type shamir Initialized true Sealed false Total Shares...

@luanphantiki It seems that the pod can connect to the leader pod of the vault, the log output of the leader is as follows: ``` 2021-10-26T09:19:43.036Z [INFO] storage.raft: starting snapshot...

@luanphantiki The backup pod error message stays the same. I could successfully connect from the backup pod to the S3 endpoint (we used minio) via `nc`: ``` ip.add.ress.minio (ip.add.ress.minio:9000) open...

@luanphantiki at first, thanks for your patience :) I started a debug pod to play around with configuration and the binary. Tried to perform a backup using this (redacted) configuration:...

@luanphantiki Ok. Is there by any chance a possibility to get more information why this step fails? It seems to be a timeout value, after 60 secs the snapshot attempt...

@luanphantiki The problem could be related with the size of the vault.db. My vault.db file is currently over 2 GB. I checked whether there's a timeout issue when creating the...

@luanphantiki You're absolutely right. Thx for your help!