# Why do the trust-manager docs advise copying a cert-manager root CA into a separate ConfigMap instead of using its Secret as a Bundle source?

cert-manager, Hard (Expert), Security. https://k8wiz.com/uquiz/why-do-the-trust-manager-docs-advise-copying-a-cert-manager-root-ca-into-a-separate-configmap-instead-of-using-its-secret-as-a-b

- A. trust-manager can't read Secrets that cert-manager owns
- B. A root rotation would drop the old root from bundles at once
- C. A Secret source also copies tls.key into every target namespace
- D. Bundles only refresh Secret sources when trust-manager restarts

**Answer:** A root rotation would drop the old root from bundles at once

**Explanation:** When the issuer's Secret gets a new root, trust-manager updates the bundle immediately and stops trusting the old root, so services still using leaves from the old root break. A separate ConfigMap lets you hold both roots during rollover and remove the old one on your own schedule. trust-manager never needs or copies tls.key, and it can read Secrets in its trust namespace.
