From a60f6a50ae716d7dd31f02915487e5ef4e1d7e94 Mon Sep 17 00:00:00 2001 From: Fang-Pen Lin Date: Thu, 11 Dec 2025 15:56:13 -0800 Subject: [PATCH] Update doc --- docs/documentation/platform/pki/k8s-cert-manager.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/platform/pki/k8s-cert-manager.mdx b/docs/documentation/platform/pki/k8s-cert-manager.mdx index f81d551b7..457522e03 100644 --- a/docs/documentation/platform/pki/k8s-cert-manager.mdx +++ b/docs/documentation/platform/pki/k8s-cert-manager.mdx @@ -139,7 +139,7 @@ The following steps show how to install cert-manager (using `kubectl`) and obtai ``` - - 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. - 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/