CertManagerIssuerResource
ClusterIssuer resource in the Aspire application model. namespace Aspire.Hosting.Kubernetes;
public sealed class CertManagerIssuerResource : Aspire.Hosting.ApplicationModel.Resource, Aspire.Hosting.ApplicationModel.IResource, Aspire.Hosting.ApplicationModel.IResourceWithParent, Aspire.Hosting.ApplicationModel.IResourceWithParent<Aspire.Hosting.Kubernetes.CertManagerResource>{ // ...}Remarks
Section titled Remarks At deploy time, an issuer is rendered to a cert-manager.io/v1 ClusterIssuer YAML document and applied to the cluster with kubectl apply after the cert-manager Helm chart is installed and its admission webhook is reachable. The manifest is not baked into the helm chart output; it is applied directly so the chart and its issuers can be managed and torn down independently.
Cluster-scoped issuers can be referenced by gateways and ingresses across all namespaces, which matches the typical multi-namespace deployment pattern for Aspire applications.
Namespace-scoped Issuer resources are intentionally not modeled in the initial release. CertManagerExtensions.AddIssuer always produces a cluster-scoped ClusterIssuer.