Component
core/security/cert-manager
A cert-manager TLS-certificate lifecycle controller for Kubernetes. cert-manager is a cluster-scoped add-on that automates the issuance and renewal of X.509 certificates from issuing sources such as ACME (Let's Encrypt), a private CA, or Vault. It extends the cluster with its own Certificate, Issuer, and ClusterIssuer custom resources; applications request certificates by declaring those resources rather than by wiring a topology edge, so the component takes no `uses` edge, and what it publishes is where Prometheus finds its metrics. The controller reconciles certificate requests, a webhook validates and defaults the custom resources, and a CA injector wires the webhook's CA bundle into the cluster. cert-manager is realized on Kubernetes through a Helm Recipe; it has no standalone local-container form, so no Compose Recipe is provided. Each of the three serves its own metrics, and their Services do not all name the metrics port alike, so the Recipe publishes the pod label selecting all three, the name of their metrics port and the path, for a scraper that discovers those pods directly.
Provenance
- Content digest
- sha256:b761e549fd28947528be4354e8b64c0f6689452fbae16048eee954bcc68de6f3
- Published
- 2026-11-10T10:13:20Z
- Signing identity
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signature
- Officialapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:53468c4d8ba63315537d340cee8403cdae5839e3ca0e0b4da20c65981b221b2b
Reference at this version
oci://hub.aggrega.ai/component/core/security/cert-manager:1.0.0Developer parameters
Values the developer sets in the Aggregate.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| install_crds | boolean | true | no | Whether this component installs cert-manager's custom resource definitions (Certificate, Issuer, ClusterIssuer, and the ACME resources). Leave on to bring the certificate API into the cluster; set false when the CRDs are managed out of band or already present. |
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| source_version | string | — | no | Source artifact version (Helm chart). Overrides the Recipe's default source version. Changing from default does not guarantee value mapping compatibility. |
| compute | object | — | no | — |
| overrides | object (open) | — | no | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Output contract
Values this component publishes to consumers over the uses topology.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| metrics_pod_selector | string | — | no | Kubernetes label selector matching the controller, webhook and CA injector pods, for a scraper that discovers those pods directly rather than scraping one address. Published beside `metrics_pod_port` and `metrics_path`. |
| metrics_pod_port | string | — | no | Name of the container port on those pods that carries the metrics, `http-metrics`. |
| metrics_path | string | — | no | Path the metrics are served at on that port, `/metrics`. |
Uses sockets
The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.
No uses sockets declared.
Attachment slots
Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.
No attachment slots declared.
Self-inject allowlist
No self-inject pipes declared.
Relationships
Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.
Uses
This entity uses nothing in the catalog.
Used by
uses socket «auth_core»
uses socket «auth_core»
uses socket «auth_core»
uses socket «auth_core»
uses socket «upstream»
uses socket «forward_target»
uses socket «scrape_target»
uses socket «store»
uses socket «jailbreak_detection»
applies to
applies to
applies to
applies to
applies to
applies to
applies to
implements