fix/workaround: allow external/alternative CAs for the client commands when using TLS.#113
Open
margau wants to merge 1 commit intovalkey-io:mainfrom
Open
fix/workaround: allow external/alternative CAs for the client commands when using TLS.#113margau wants to merge 1 commit intovalkey-io:mainfrom
margau wants to merge 1 commit intovalkey-io:mainfrom
Conversation
Signed-off-by: Vanessa Gaube <dev@vanessagaube.de>
Collaborator
|
Hi @margau, thanks for the PR. I understand the principle, CAs sometimes has to be provided outside of the TLS secret. The only concern I have is that the logic of using an alternate path is spread across many places, and it will only grow after Sentinel/Cluster is implemented. I believe the exporter sidecar will also need handling. I would rather add the logic in |
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.
Recently, I ran into a problem with TLS certs:
I'm using a TLS Cert by cert-manager using ACME. In the secret generated with cert-manager, there is no separate CA available (see the topics on ca.crt in https://cert-manager.io/docs/usage/certificate/#target-secret).
Therefore, I needed a separate way of using another CA for the
valkey-cliclient (mainly for probes).This PR adds a value that allows the client to use any other ca.
In my case the cacerts provided by trust-manager into a config map and mounted using the
extraValkeyConfigs.Using the
fullchainakatls.crt, which is provided to the server as ca file from the TLS-secret, does not work:Given the above example, setting
tls.alternativeClientCa: "/cacert/valkey-trust-bundle.crt"should make it work also for the probes./cacert/is the mount of trust-manager, which creates a configmap with all CAs necessary, e.g. using the following bundle:Please let me know in case there is a better way solving this.
Thanks!