More docs

This commit is contained in:
Fang-Pen Lin
2025-11-24 16:57:37 -08:00
parent c272c0552c
commit 44fc9d1f18
2 changed files with 2 additions and 2 deletions

View File

@@ -25,7 +25,7 @@ When you deploy a `Certificate` CRD in your workload cluster, `cert-manager` use
Infisical verifies the request against your certificate templates and returns the signed certificate.
From there, Istio's control plane will automatically use this intermediate CA to sign leaf certificates for workloads in the service mesh, enabling secure mTLS communication across your entire Gloo Mesh infrastructure.
Follow the [Kubernetes cert-manager guide](/documentation/platform/pki/k8s-cert-manager) for detailed instructions on how to set up the Infisical PKI Issuer and cert-manager for your Istio intermediate CA certificates in Gloo Mesh clusters.
Follow the [Kubernetes cert-manager guide](/documentation/platform/pki/k8s-cert-manager) for detailed instructions on how to set up the Infisical PKI ACME certificate profile and cert-manager for your Istio intermediate CA certificates in Gloo Mesh clusters.
For Gloo Mesh-specific configuration, ensure that:

View File

@@ -252,7 +252,7 @@ The following steps show how to install cert-manager (using `kubectl`) and obtai
The full list of the fields supported on the `Certificate` resource can be found in the API reference documentation [here](https://cert-manager.io/docs/reference/api-docs/#cert-manager.io/v1.CertificateSpec).
<Note>
Currently, not all fields are supported by the Infisical PKI Issuer.
Currently, not all fields are supported by the Infisical PKI ACME server.
</Note>
</Accordion>