DNM: proof of concept for self-signed cert volume mount #186
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://phabricator.wikimedia.org/T383335
This is only a proof of concept I wanted to share how we can use our self-signed CA certificates into a tool deployment by only using a volume mount from the k8s secret. This approach is super hacky as the file it mounts to usually contains all the certificates that live in /etc/ssl/certs. Normally you would add the cert under /usr/share/ca-certificates/ and run
update-ca-certificates, but this would require us to either know the cert at image buildtime or to use something like an k8s operator or something to inject this later.