Update doc

This commit is contained in:
Fang-Pen Lin
2025-12-11 16:09:59 -08:00
parent f769f3a1a0
commit a60f6a50ae
@@ -139,7 +139,7 @@ The following steps show how to install cert-manager (using `kubectl`) and obtai
``` ```
<Note> <Note>
- Currently, the Infisical ACME server only supports the HTTP-01 challenge. Support for DNS-01 is planned for a future release. If domain ownership validation is not desired, you can disable it by enabling the `Skip DNS ownership validation` option in your ACME certificate profile configuration. - Currently, the Infisical ACME server only supports the HTTP-01 challenge. Support for DNS-01 is planned for a future release. If domain ownership validation is not desired, you can disable it by enabling the `Skip DNS ownership validation` option in your ACME certificate profile configuration. Please read [the document for ACME certificate profile](/documentation/platform/pki/enrollment-methods/acme) to learn more.
- An `Issuer` is namespace-scoped. Certificates can only be issued using an `Issuer` that exists in the same namespace as the `Certificate` resource. - An `Issuer` is namespace-scoped. Certificates can only be issued using an `Issuer` that exists in the same namespace as the `Certificate` resource.
- If you need to issue certificates across multiple namespaces with a single resource, create a `ClusterIssuer` instead. The configuration is identical except `kind: ClusterIssuer` and no `metadata.namespace`. - If you need to issue certificates across multiple namespaces with a single resource, create a `ClusterIssuer` instead. The configuration is identical except `kind: ClusterIssuer` and no `metadata.namespace`.
- More details: https://cert-manager.io/docs/configuration/acme/ - More details: https://cert-manager.io/docs/configuration/acme/