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

[question]: Provisioning db user and password from dynamic vault store to workflows #130

Closed
2 tasks done
wesbragagt opened this issue Sep 10, 2024 · 3 comments
Closed
2 tasks done

[question]: Provisioning db user and password from dynamic vault store to workflows #130

wesbragagt opened this issue Sep 10, 2024 · 3 comments
Assignees
@fullykubed
Labels
question Further information is requested

Comments

@wesbragagt
Copy link
Contributor

Prior Search

  • I have already searched this project's issues to determine if a similar question has already been asked.

What is your question?

I have an async job that I run in kubernetes and I would love to instead using the root credentials to use the vault dynamic credentials provisioning to the job. I'm looking for recommendations in the terraform modules on how to accomplish that. I've heard of vault csi provider but I'm struggling to understand how to implement that with the stack.

What primary components of the stack does this relate to?

terraform

Code of Conduct

  • I agree to follow this project's Code of Conduct
@wesbragagt wesbragagt added question Further information is requested triage Needs to be triaged labels Sep 10, 2024
@fullykubed
Copy link
Member

Currently we do not have direct support for mounting vault secrets in pods. However, its something we were already planning on adding, so I will bump this up in priority to be included in the next release.

@fullykubed fullykubed removed the triage Needs to be triaged label Sep 10, 2024
@fullykubed
Copy link
Member

The code for this is completed and will be included in the next release.

@wesbragagt
Copy link
Contributor Author

@fullykubed I just looked through the change. I'm so pumped for this addition. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fullykubed fullykubed

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fullykubed @wesbragagt