You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Managed to use Tiller well with a Hashicorp v1 k/v Vault.
However we're finding challenges Tiller not converting secrets for a v2 k/v Vault.
On Hashicorp's website v2 Vaults need to add in 'data' to the path of the k/v path, if using their API.
Do we need to do the same for Tiller and adjust the value somewhere? And if so, what is a working example? (As we get 405 errors when trying different variations of inserting 'data' to the path, etc).
Or is it more that Tiller needs to have an update to adjust for any v2 k/v Vaults by Hashicorp?
The text was updated successfully, but these errors were encountered:
@markround should we consider tiller to be stalled / unmaintained in terms that you moved on to other areas? no offense at all, just a question for us to plan with. I open a dedicated issue for that so you can comment on it #75
Managed to use Tiller well with a Hashicorp v1 k/v Vault.
However we're finding challenges Tiller not converting secrets for a v2 k/v Vault.
On Hashicorp's website v2 Vaults need to add in 'data' to the path of the k/v path, if using their API.
Do we need to do the same for Tiller and adjust the value somewhere? And if so, what is a working example? (As we get 405 errors when trying different variations of inserting 'data' to the path, etc).
Or is it more that Tiller needs to have an update to adjust for any v2 k/v Vaults by Hashicorp?
The text was updated successfully, but these errors were encountered: