You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version `1.16.0` of the {cert-manager-operator} is based on the upstream cert-manager version `v1.16.4`. For more information, see the link:https://cert-manager.io/docs/releases/release-notes/release-notes-1.16/#v1164[cert-manager project release notes for v1.16.4].
With this release, the {cert-manager-operator} has been verified to be mirrored to and installed in a disconnected environment.
35
+
36
+
The Operator has also been validated to work with the following issuer types in disconnected environments: ACME, CA, Self-signed, and Vault.
37
+
Specifically, private or self-hosted ACME servers have been validated, as Let's Encrypt or other public ACME services are not feasible options in disconnected environments.
38
+
The oc-mirror plugin v2 is the preferred method to mirror Operator images.
39
+
For more information, see xref:../../disconnected/mirroring/about-installing-oc-mirror-v2.adoc#about-installing-oc-mirror-v2[Mirroring images for a disconnected installation by using the oc-mirror plugin v2].
40
+
41
+
*Extended operand metrics support*
42
+
43
+
With this release, cert-manager webhook and cainjector operands now expose Prometheus metrics on port 9402 by default via the `/metrics` service endpoint.
44
+
You can configure OpenShift Monitoring to collect metrics from all cert-manager operands by enabling the built-in user workload monitoring stack.
45
+
For more information, see xref:../../security/cert_manager_operator/cert-manager-monitoring.adoc#cert-manager-monitoring[Monitoring {cert-manager-operator}].
46
+
47
+
*Streaming Lists enablement*
48
+
49
+
With this release, the {cert-manager-operator} now uses the new upstream WatchListClient feature.
50
+
This enables use of the Streaming Lists feature of the Kubernetes API server, which reduces the load on the API server.
51
+
The peak memory use of the cert-manager components when they start up is optimized on {product-title} 4.14 and later.
0 commit comments