Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

consul-helm: Support using Vault for all secrets #656

Closed
lkysow opened this issue Jan 22, 2021 · 6 comments
Closed

consul-helm: Support using Vault for all secrets #656

lkysow opened this issue Jan 22, 2021 · 6 comments

Comments

@lkysow
Copy link
Member

lkysow commented Jan 22, 2021

Would be great to support be able to retrieve all secret material: ACL tokens, TLS certs, etc. from Vault.
@shellfu
Copy link

shellfu commented Jan 22, 2021

This would make upgrades/rebuilds immensely easier. If any code contribution is needed for this I will dedicate the time if so desired.

@david-yu
Copy link
Contributor

david-yu commented Apr 2, 2021

@shellfu Could you give us more details on how that would upgrades/rebuilds easier? Do you currently also use Vault today?

@shellfu
Copy link

shellfu commented Apr 8, 2021

Yes, we currently use Vault to manage the majority of our secrets. Having Vault manage the certificates in the context of K8s would be ideal as rotations could be managed in Vault vs on Kube.

@t-eckert t-eckert changed the title Support using Vault for all secrets helm:Support using Vault for all secrets Aug 24, 2021
@t-eckert t-eckert transferred this issue from hashicorp/consul-helm Aug 24, 2021
@david-yu david-yu changed the title helm:Support using Vault for all secrets consul-helm: Support using Vault for all secrets Oct 20, 2021
@ultrafear
Copy link

Any updates on this feature?

@ishustava
Copy link
Contributor

We're working on it right now. Stay tuned!

@david-yu
Copy link
Contributor

david-yu commented Dec 7, 2021

Closing as this is mostly addressed by: #904. We'll work on addressing the multi-dc capabilities in a future release.

@david-yu david-yu closed this as completed Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@david-yu @lkysow @shellfu @ishustava @ultrafear