-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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.
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
connect: certificate chain to contain root cert #6613
Comments
Hey there, Feel free to check out the community forum as well! |
i believe it is; nothing in the change log seems to indicate otherwise. |
Thank you for opening this issue! I created #11598 which I believe describes a way to solve this problem. |
Closed by #11910 |
I'm trying to establish trust between a consul connect cluster and a kube cluster.
I'm setting the root-cert in consul connect, and trying to send requests from outside the cluster.
The request are being rejected by the client in the kube cluster - it complains that the CA is invalid. I believe that the reason is that consul doesn't set the cert chain correctly.
in the config dump of the envoy sidecar in consul (i.e.
connect envoy -sidecar-for
), i see:Note that: the
certificate_chain
contain only the leaf certificate, andtrusted_ca
contains the root and intermediary cert.I would expect that the
certificate_chain
to contain the certs up to the root, and that thetrusted_ca
would only contain the root cert, like so:What is the reason for the current design? Would you consider the suggested change reasonable?
Consul info for both Client and Server
Server \ Client info
The text was updated successfully, but these errors were encountered: