You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @ssengar - Thanks for raising this question. The normal way I would think about tackling this would be to provide a certificate bundle that includes the root certificates of all the required trusted CAs.
The general steps to do that would be something like:
Obtain the root certificate files for all the CAs you want to trust.
Concatenate all the root certificate files into a single bundle file.
Configure etcd to use the certificate bundle file. This involves specifying the file path in the etcd configuration file or providing it as a command-line argument when starting etcd.
Have you tried an approach like this?
Note: There is an active issue around the refreshing of ca bundles for new connections, i.e. zero downtime updates. Refer: #11555. Just something to be aware of.
We are trying to consolidate the channels to which questions for help/support are posted so that we can improve our efficiency in responding to your requests, and to make it easier for you to find answers to frequently asked questions and how to address common use cases.
We regularly see messages posted in multiple forums, with the full response thread only in one place or, worse, spread across multiple forums. Also, the large volume of support issues on GitHub is making it difficult for us to use issues to identify real bugs.
Members of the etcd community use Discussion Forums to field support requests. Before posting a new question, please search these for answers to similar questions, and also familiarize yourself with:
What would you like to be added?
multiple CA's should be trusted by etcd.
Why is this needed?
as part of our setup we might need etcd clients to connect to etcd via certificates issued by thier own CA.
The text was updated successfully, but these errors were encountered: