awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-03 19:26:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update k8s doc

Browse Source
This commit is contained in:
Fang-Pen Lin
2025-12-11 16:09:55 -08:00
parent f50a0ca838
commit f6d20be7eb
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/documentation/platform/pki/k8s-cert-manager.mdx
+1 -1
View File
@@ -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 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. - 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/