Use vault CA instead of Consul CA in consul OSS helm chart

[abdel19792]

Thanks David, is it mandatory to have vault acting as root CA ?
my case is somehow similar to this

Consul Connect: Vault as a CA, with root CA as some other vault instance

Hi, Currently, I see that RootPKIPath is a mandatory param while specifying vault as a CA for consul connect. What can be done in a scenario where my intermediate CA is a vault instance configured to serve as a CA for consul connect and my root CA is some other vault instance ? Regards, Ashwin

Vault CA with offline root as Consul Connect CA?

I’ve had Vault PKI set up for a little while where Vault operates as an intermediate CA, signed by an offline root. Now I’m looking at Consul Connect and find it wants both a root and intermediate to manage in Vault. Is it supported to point root_pki_path to the current Vault intermediate pki engine and use a second-level intermediate pki engine for intermediate_pki_path, or is an online root in Vault really required?