Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

Support Vault 0.11 and greater #354

Closed
azuretek opened this issue Oct 22, 2018 · 4 comments
Closed

Support Vault 0.11 and greater #354

azuretek opened this issue Oct 22, 2018 · 4 comments

Comments

@azuretek
Copy link

I love the vault operator, it simplifies a lot of the issues around deploying vault in a redundant way with ephemeral storage. Also the simplicity of backing up and restoring is great too.

The only issues is that we're stuck on an old version of vault and we want to upgrade. Is there a reason the operator can't just run a publicly available vault image? As far as I can tell all the vault API endpoints in use haven't changed between v0.9 and v0.11, and I'm not aware of any custom modifications to vault that allow the operator to function.

Is there a reason we can't support the newer versions of vault?

@azuretek
Copy link
Author

So I was able to upgrade by creating a vault image that installs curl and bash and setting my baseImage and version to match my docker image.

Apparently that's all that's required to make this work, though I don't understand why the image isn't provided by the maintainers of this project.

@ficofer
Copy link

ficofer commented Nov 8, 2018

@azuretek I been trying to do this to win GUI capabilities do you have a readme or step by step of your docker file to have as a base ?

@bazzilio
Copy link

look to #332

@azuretek
Copy link
Author

azuretek commented May 2, 2019

@ficofer sorry for the late response but for posterity here's our docker file

FROM vault:0.11.5

RUN apk add --no-cache curl

You'll want to pin that to whatever version you need.

@azuretek azuretek closed this as completed May 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants