We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Is it linked to a user story? (use the "#" to tag the user story) No
What do we want to build? Automatic directory creation for /opt/vault-kms on control plane to write the socket file.
/opt/vault-kms
Why do we want to build it? Currently a manual process which slows down the deployment / creating friction in some environment.
How do we want to design it? Through an initContainer
What do we want to build? An initContainer to access the control plane file system, create, mount the directory /opt/vault-kms
The text was updated successfully, but these errors were encountered:
DaemonSet defintion used within #31 auto-create the /opt/vault-kms on the control plane as expected location. Closing this RFE against RFE #31
Sorry, something went wrong.
mhmxs
vfiftyfive
andytyler
romdalf
cannischan
otherjamesbrown
Successfully merging a pull request may close this issue.
Is it linked to a user story? (use the "#" to tag the user story)
No
What do we want to build?
Automatic directory creation for
/opt/vault-kms
on control plane to write the socket file.Why do we want to build it?
Currently a manual process which slows down the deployment / creating friction in some environment.
How do we want to design it?
Through an initContainer
What do we want to build?
An initContainer to access the control plane file system, create, mount the directory
/opt/vault-kms
The text was updated successfully, but these errors were encountered: