From f6d20be7eb5331ce910e20acb08a9f84e6bdb08c Mon Sep 17 00:00:00 2001 From: Fang-Pen Lin Date: Thu, 11 Dec 2025 15:13:47 -0800 Subject: [PATCH] Update k8s 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 b0f696ba9..f81d551b7 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 and requires successful challenge completion before issuing certificates. Support for optional challenges and DNS-01 is planned for a future release. + - 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. - 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/