https://docs.protegrity.com/aiteam-edition/docs/infrastructure/additional_info/Recent content in Additional Information onHugoenhttps://docs.protegrity.com/aiteam-edition/docs/infrastructure/additional_info/cert_mgmt/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/aiteam-edition/docs/infrastructure/additional_info/cert_mgmt/<p>In a PPC deployment, Envoy and other internal components rely on a CA to establish trusted TLS communication.</p> <p>By default, PPC uses an internally generated CA. PPC supports replacing the default CA with a custom CA that can be preserved and reused across cluster restore or migration.</p> <h2 id="prerequisites">Prerequisites</h2> <p>Before you begin, ensure that:</p> <ul> <li>You have access to the PPC Kubernetes cluster (kubectl configured).</li> <li>Openssl is installed.</li> <li>Cert-manager is installed.</li> <li>The <code>eclipse-issuer</code> ClusterIssuer exists.</li> <li>You have permission to create secrets in the cert-manager namespace.</li> </ul> <p>Perform the following steps:</p>