feat(deploy/chart): optional networkPolicy for more containers by jcpunk · Pull Request #8370 · cert-manager/cert-manager

jcpunk · 2025-12-26T16:45:34Z

Fixes: #8369
Fixes: #8285

Pull Request Motivation

This PR merges the webhook policies into a single template and adds optional policies for the controller and the cainjector.

Kind

/kind feature

Release Note

Add a set of flags to permit setting NetworkPolicy across all deployed containers.
Remove redundant global IP ranges from example policies.

CyberArk tracker: VC-48226

cert-manager-prow · 2025-12-26T16:45:45Z

Hi @jcpunk. Thanks for your PR.

I'm waiting for a cert-manager member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

hjoshi123

Overall I am not opposed to the idea.. but do have some feedbacks.. Also would defer to others to see if there are any other ports that need to be added to the default list

Maybe we also want to consider this #8285 and keep the egress.to list empty to allow everything?

deploy/charts/cert-manager/templates/networkpolicy-webhooks.yaml

deploy/charts/cert-manager/values.yaml

jcpunk · 2025-12-29T14:49:22Z

Tested on Cilium 1.18, with no IP block specified the egress filtering appears to work on my bare metal cluster allowing connectivity to the API server and DNS.

hjoshi123 · 2025-12-29T15:32:25Z

/ok-to-test

jcpunk · 2025-12-29T16:45:33Z

I think I've sorted the tests...

jcpunk · 2025-12-29T18:21:30Z

I don't think these latest failures are me?

erikgb · 2025-12-29T19:21:49Z

/test pull-cert-manager-master-e2e-v1-34

hjoshi123 · 2025-12-31T16:03:57Z

/test pull-cert-manager-master-e2e-v1-35

jcpunk · 2026-01-02T17:31:07Z

PR Rebased.

hjoshi123 · 2026-01-07T15:13:42Z

@jcpunk could you add a release label to this since this is a user facing change?

jcpunk · 2026-01-07T15:26:00Z

Sure... umm, how do I do that?

erikgb · 2026-01-07T15:40:29Z

@jcpunk, you just have to edit the release note block I just added to the PR description. It is part of our PR template, but somehow it is gone.

jcpunk · 2026-01-07T16:10:26Z

Done, does that look OK?

wallrj-cyberark

Consider adding a links to https://cert-manager.io/docs/installation/best-practice/#network-requirements-and-network-policy in the the values.yaml comments,
so that Helm users can discover more about cert-manager + Network Policy.

And after we merge this, we should also update the best-practices documentation to explain how to use the builtin network policy features of the Helm chart.

https://cert-manager.io/docs/installation/best-practice/#network-requirements-and-network-policy
https://github.com/cert-manager/website/blob/master/content/docs/installation/best-practice.md
And we should update the best-practices helm chart values so that these new values are tested by our periodic E2E tests:
https://github.com/cert-manager/website/blob/master/public/docs/installation/best-practice/values.best-practice.yaml

Please ping the people who have commented on #2334 and ask them if this change will help them?

#2334

wallrj-cyberark · 2026-01-09T11:45:41Z

deploy/charts/cert-manager/values.yaml

-      - ipBlock:
-          cidr: 0.0.0.0/0
-      - ipBlock:
-          cidr: "::/0"


@jcpunk In the PR description you describe these as redundant, but are you sure?

In #7726 you added this IPv6 configuration. Have you learned more about the defaults for these fields since then?

Please link to some documentation showing the network policy defaults, so that we can be confident that cilium, calico and other similar products will all treat an empty to as allow.

I've learned a bit about the defaults since then. Initially I added this as my IPv6 cluster had problems. However, since then I've discovered that if no ipBlock is specified, then no filtering on the IP range is performed. In effect, setting the ipBlock to those ranges was equivalent to leaving it unset, but with extra burden placed on the CNI to filter against an unlimited range. I migrated from calico to cilium, in my environment the removal of the ipBlock caused no issues. It in fact fixed an issue where cilium (tested with 1.18.3) wouldn't deliver the packets if the larger ipBlock was specified.

https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.35/#networkpolicyegressrule-v1-networking-k8s-io

My reading of "If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination)." is that we can safely drop the "any IPv4 and any IPv6" restriction as we are aiming for unrestricted.

wallrj-cyberark · 2026-01-09T11:59:20Z

deploy/charts/cert-manager/templates/networkpolicy-cert-manager.yaml

+  ingress:
+    {{- with .Values.networkPolicy.ingress }}
+      {{- toYaml . | nindent 2 }}
+    {{- end }}


Did you consider adding rules for the metrics port and pprof ports, if those features have been configured elsewhere in the Helm values?
It would be more convenient for users, but would add complexity to the chart.

The existing webhook ingress policy doesn't do that, so I suppose doing it this way provides consistency with what we already have.

And another advantage of doing it this way is that it keeps the Helm chart logic simple.

The default ingress I've got in the chart allows all traffic on all ports. I'd love to restrict this further, but I wasn't super confident in my knowledge of how to ensure if folks customize ports that the defaults would still work. If all the ports are named it should be workable...

I've updated the defaults to restrict the traffic to the named ports on each Deployment. I love the idea of setting stronger defaults, but was worried it might sidetrack the review. :)

wallrj-cyberark · 2026-01-09T12:08:55Z

deploy/charts/cert-manager/values.yaml

 nodeSelector:
  kubernetes.io/os: linux

+# Enables default network policies for cert-manager.


Write more about what the defaults are and explain why users may wish to enable these and why they are disabled by default.
When @mjudeikis introduced NetworkPolicy to the Helm chart, in #5417 it at least said:

See NetworkPolicy documentation

But those words got lost somewhere in the Git history....I can't find where.

But in any case, I think we need to help users understand why they should enable NetworkPolicy and how to configure it.

In theory I've added the doc that was missing and provided some more information on what defaults were selected and why. In practice, is it enough? I didn't want to toss too much in and make a wall of text folks ignore...

Fixes: cert-manager#8369 Signed-off-by: Pat Riehecky <riehecky@fnal.gov>

wallrj-cyberark

@jcpunk Sorry it's taken me ages to test this, but I finally managed to get the E2E tests passing when using these new NetworkPolicy defaults, plus some additional egress rules for the various in-cluster services, such as pebble, bind, and vault.

I've documented those additional rules as examples for the documentation here:

cert-manager/website#1911

And when this and that PR have merged, we can ask someone to review #8387 which configures the cert-manager nightly "best-practice" E2E tests to run with NetworkPolicy enabled.

#8387

wallrj · 2026-01-16T14:41:52Z

/approve
/lgtm

cert-manager-prow · 2026-01-16T14:42:00Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avani8507, wallrj, wallrj-cyberark

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [wallrj]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

wallrj-cyberark · 2026-01-16T15:04:18Z

deploy/charts/cert-manager/values.yaml

+    egress:
+    - ports:
+      - port: 80
+        protocol: TCP


The cainjector does not connect to port 80. That's only necessary for the controller to perform HTTP01 self-checks.
I'll remove this (and from the webhook rules) in a followup PR.

wallrj-cyberark · 2026-01-16T15:07:34Z

@jcpunk: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-cert-manager-master-e2e-v1-35 a0c521d link unknown /test pull-cert-manager-master-e2e-v1-35
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

I see this the logs:

Jan 16 15:01:38.170: INFO: Expected Issuer acme-issuer-http01-5wggd condition Ready=True but it has: [{Ready False 2026-01-16 14:59:38 +0000 UTC ErrRegisterACMEAccount Failed to register ACME account: Post "https://pebble.pebble.svc.cluster.local/sign-me-up": net/http: request canceled (Client.Timeout exceeded while awaiting headers) 1}] (took 5m0s)

But I'm not sure why. Those tests are running with NetworkPolicy disabled (the default).
Perhaps a test flake (pebble crashing or hanging) but it's not clear why, in that case.
I see the same errors here in the recent cert-manager 1.18 periodic tests, which is confusing, but gives reassurance that the errors are not related to the changes in this PR:

/retest

wallrj-cyberark · 2026-02-03T14:06:01Z

📢 The fix or feature is now available for testing

https://github.com/cert-manager/cert-manager/releases/tag/v1.20.0-alpha.1

Please test and report back.

…#4581) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [cert-manager/cert-manager](https://github.com/cert-manager/cert-manager) | minor | `v1.19.4` → `v1.20.0` | --- ### Release Notes <details> <summary>cert-manager/cert-manager (cert-manager/cert-manager)</summary> ### [`v1.20.0`](https://github.com/cert-manager/cert-manager/releases/tag/v1.20.0) [Compare Source](cert-manager/cert-manager@v1.19.4...v1.20.0) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.20.0 adds support for the new ListenerSet resource, adds support for Azure Private DNS; parentRefs are no longer required when using ACME with Gateway API, and OtherNames was promoted to Beta. #### Changes by Kind ##### Feature - Added a set of flags to permit setting NetworkPolicy across all deployed containers. Remove redundant global IP ranges from example policies. ([#8370](cert-manager/cert-manager#8370), [@jcpunk](https://github.com/jcpunk)) - Added selectable fields to custom resource definitions for .spec.issuerRef.{group, kind, name} ([#8256](cert-manager/cert-manager#8256), [@tareksha](https://github.com/tareksha)) - Added support for specifying `imagePullSecrets` in the `startupapicheck-job` Helm template to enable pulling images from private registries. ([#8186](cert-manager/cert-manager#8186), [@mathieu-clnk](https://github.com/mathieu-clnk)) - Added 'extraContainers' helm chart value, allowing the deployment of arbitrary sidecar containers within the cert-manager operator pod. This can be used to support, for e.g., AWS IAM Roles Anywhere for Route53 DNS01 verification. ([#8355](cert-manager/cert-manager#8355), [@dancmeyers](https://github.com/dancmeyers)) - Added `parentRef` override annotations on the Certificate resource. ([#8518](cert-manager/cert-manager#8518), [@hjoshi123](https://github.com/hjoshi123)) - Added support for azure private zones for dns01 issuer. ([#8494](cert-manager/cert-manager#8494), [@hjoshi123](https://github.com/hjoshi123)) - Added support for configuring PEM decoding size limits, allowing operators to handle larger certificates and keys. ([#7642](cert-manager/cert-manager#7642), [@robertlestak](https://github.com/robertlestak)) - Added support for unhealthyPodEvictionPolicy in PodDisruptionBudget ([#7728](cert-manager/cert-manager#7728), [@jcpunk](https://github.com/jcpunk)) - For Venafi provider, read `venafi.cert-manager.io/custom-fields` annotation on Issuer/ClusterIssuer and use it as base with override/append capabilities on Certificate level. ([#8301](cert-manager/cert-manager#8301), [@k0da](https://github.com/k0da)) - Improve error message when CA issuers are misconfigured to use a clashing secret name ([#8374](cert-manager/cert-manager#8374), [@majiayu000](https://github.com/majiayu000)) - Introduce a new Ingress annotation `acme.cert-manager.io/http01-ingress-ingressclassname` to override `http01.ingress.ingressClassName` field in HTTP-01 challenge solvers. ([#8244](cert-manager/cert-manager#8244), [@lunarwhite](https://github.com/lunarwhite)) - Update `global.nodeSelector` to helm chart to perform a `merge` and allow for a single `nodeSelector` to be set across all services. ([#8195](cert-manager/cert-manager#8195), [@StingRayZA](https://github.com/StingRayZA)) - Vault issuers will now include the Vault server address as one of the default audiences on generated service account tokens. ([#8228](cert-manager/cert-manager#8228), [@terinjokes](https://github.com/terinjokes)) - Added experimental `XListenerSet` feature gate ([#8394](cert-manager/cert-manager#8394), [@hjoshi123](https://github.com/hjoshi123)) ##### Documentation - Add GWAPI documentation to NOTES.TXT in helm chart ([#8353](cert-manager/cert-manager#8353), [@jaxels10](https://github.com/jaxels10)) ##### Bug or Regression - Adds logs for cases when acme server returns us a fatal error in the order controller ([#8199](cert-manager/cert-manager#8199), [@Peac36](https://github.com/Peac36)) - Fixed an issue where kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed ([#8160](cert-manager/cert-manager#8160), [@inteon](https://github.com/inteon)) - Changes to the Duration and RenewBefore annotations on ingress and gateway-api resources will now trigger certificate updates. ([#8232](cert-manager/cert-manager#8232), [@eleanor-merry](https://github.com/eleanor-merry)) - Fix an issue where ACME challenge TXT records are not cleaned up when there are many resource records in CloudDNS. ([#8456](cert-manager/cert-manager#8456), [@tkna](https://github.com/tkna)) - Fix unregulated retries with the DigitalOcean DNS-01 solver Add full detailed DNS-01 errors to the events attached to the Challenge, for easier debugging ([#8221](cert-manager/cert-manager#8221), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. ([#8403](cert-manager/cert-manager#8403), [@calm329](https://github.com/calm329)) - Fixed an issue where HTTP-01 challenges failed when the Host header contains an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. ([#8424](cert-manager/cert-manager#8424), [@SlashNephy](https://github.com/SlashNephy)) - Fixed the HTTP-01 Gateway solver creating invalid HTTPRoutes by not setting spec.hostnames when the challenge DNSName is an IP address. ([#8443](cert-manager/cert-manager#8443), [@alviss7](https://github.com/alviss7)) - Revert API defaults for issuer reference kind and group introduced in 0.19.0 ([#8173](cert-manager/cert-manager#8173), [@erikgb](https://github.com/erikgb)) - Security (MODERATE): Fix a potential panic in the cert-manager controller when a DNS response in an unexpected order was cached. If an attacker was able to modify DNS responses (or if they controlled the DNS server) it was possible to cause denial of service for the cert-manager controller. ([#8469](cert-manager/cert-manager#8469), [@SgtCoDFish](https://github.com/SgtCoDFish)) - Update Go to `v1.25.5` to fix `CVE-2025-61727` and `CVE-2025-61729` ([#8290](cert-manager/cert-manager#8290), [@octo-sts](https://github.com/octo-sts)\[bot]) - When Prometheus monitoring is enabled, the metrics label is now set to the intended value of `cert-manager`. Previously, it was set depending on various factors (namespace cert-manager is installed in and/or Helm release name). ([#8162](cert-manager/cert-manager#8162), [@LiquidPL](https://github.com/LiquidPL)) ##### Other (Cleanup or Flake) - Promoted the OtherNames feature to Beta and enabled it by default ([#8288](cert-manager/cert-manager#8288), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Promoting `xlistenerset` feature gate to `listenerset` ([#8501](cert-manager/cert-manager#8501), [@hjoshi123](https://github.com/hjoshi123)) - Rebranding of the Venafi Issuer to CyberArk ([#8215](cert-manager/cert-manager#8215), [@iossifbenbassat123](https://github.com/iossifbenbassat123)) - Switched to SSA for challenge finalizer updates ([#8519](cert-manager/cert-manager#8519), [@inteon](https://github.com/inteon)) - The default container user (UID) is now 65532 (previously 1000) and the default container group (GID) is now 65532 (previously 0) ([#8408](cert-manager/cert-manager#8408), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - The feature-gate DefaultPrivateKeyRotationPolicyAlways moved from Beta to GA and can no longer be disabled. ([#8287](cert-manager/cert-manager#8287), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Update cert-manager's ACME client, forked from golang/x/crypto ([#8268](cert-manager/cert-manager#8268), [@SgtCoDFish](https://github.com/SgtCoDFish)) - Use the latest version of Kyverno (1.16.2) in the best-practice installation tests ([#8389](cert-manager/cert-manager#8389), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - We stopped testing with Coutour due to it not supporting the new XListenerSet resource, and moved to kgateway. ([#8426](cert-manager/cert-manager#8426), [@hjoshi123](https://github.com/hjoshi123)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://gitea.alexlebens.dev/alexlebens/infrastructure/pulls/4581 Co-authored-by: Renovate Bot <renovate-bot@alexlebens.net> Co-committed-by: Renovate Bot <renovate-bot@alexlebens.net>

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [cert-manager](https://cert-manager.io) ([source](https://github.com/cert-manager/cert-manager)) | minor | `v1.19.4` → `v1.20.0` | --- ### Release Notes <details> <summary>cert-manager/cert-manager (cert-manager)</summary> ### [`v1.20.0`](https://github.com/cert-manager/cert-manager/releases/tag/v1.20.0) [Compare Source](cert-manager/cert-manager@v1.19.4...v1.20.0) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.20.0 adds support for the new ListenerSet resource, adds support for Azure Private DNS; parentRefs are no longer required when using ACME with Gateway API, and OtherNames was promoted to Beta. #### Changes by Kind ##### Feature - Added a set of flags to permit setting NetworkPolicy across all deployed containers. Remove redundant global IP ranges from example policies. ([#8370](cert-manager/cert-manager#8370), [@jcpunk](https://github.com/jcpunk)) - Added selectable fields to custom resource definitions for .spec.issuerRef.{group, kind, name} ([#8256](cert-manager/cert-manager#8256), [@tareksha](https://github.com/tareksha)) - Added support for specifying `imagePullSecrets` in the `startupapicheck-job` Helm template to enable pulling images from private registries. ([#8186](cert-manager/cert-manager#8186), [@mathieu-clnk](https://github.com/mathieu-clnk)) - Added 'extraContainers' helm chart value, allowing the deployment of arbitrary sidecar containers within the cert-manager operator pod. This can be used to support, for e.g., AWS IAM Roles Anywhere for Route53 DNS01 verification. ([#8355](cert-manager/cert-manager#8355), [@dancmeyers](https://github.com/dancmeyers)) - Added `parentRef` override annotations on the Certificate resource. ([#8518](cert-manager/cert-manager#8518), [@hjoshi123](https://github.com/hjoshi123)) - Added support for azure private zones for dns01 issuer. ([#8494](cert-manager/cert-manager#8494), [@hjoshi123](https://github.com/hjoshi123)) - Added support for configuring PEM decoding size limits, allowing operators to handle larger certificates and keys. ([#7642](cert-manager/cert-manager#7642), [@robertlestak](https://github.com/robertlestak)) - Added support for unhealthyPodEvictionPolicy in PodDisruptionBudget ([#7728](cert-manager/cert-manager#7728), [@jcpunk](https://github.com/jcpunk)) - For Venafi provider, read `venafi.cert-manager.io/custom-fields` annotation on Issuer/ClusterIssuer and use it as base with override/append capabilities on Certificate level. ([#8301](cert-manager/cert-manager#8301), [@k0da](https://github.com/k0da)) - Improve error message when CA issuers are misconfigured to use a clashing secret name ([#8374](cert-manager/cert-manager#8374), [@majiayu000](https://github.com/majiayu000)) - Introduce a new Ingress annotation `acme.cert-manager.io/http01-ingress-ingressclassname` to override `http01.ingress.ingressClassName` field in HTTP-01 challenge solvers. ([#8244](cert-manager/cert-manager#8244), [@lunarwhite](https://github.com/lunarwhite)) - Update `global.nodeSelector` to helm chart to perform a `merge` and allow for a single `nodeSelector` to be set across all services. ([#8195](cert-manager/cert-manager#8195), [@StingRayZA](https://github.com/StingRayZA)) - Vault issuers will now include the Vault server address as one of the default audiences on generated service account tokens. ([#8228](cert-manager/cert-manager#8228), [@terinjokes](https://github.com/terinjokes)) - Added experimental `XListenerSet` feature gate ([#8394](cert-manager/cert-manager#8394), [@hjoshi123](https://github.com/hjoshi123)) ##### Documentation - Add GWAPI documentation to NOTES.TXT in helm chart ([#8353](cert-manager/cert-manager#8353), [@jaxels10](https://github.com/jaxels10)) ##### Bug or Regression - Adds logs for cases when acme server returns us a fatal error in the order controller ([#8199](cert-manager/cert-manager#8199), [@Peac36](https://github.com/Peac36)) - Fixed an issue where kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed ([#8160](cert-manager/cert-manager#8160), [@inteon](https://github.com/inteon)) - Changes to the Duration and RenewBefore annotations on ingress and gateway-api resources will now trigger certificate updates. ([#8232](cert-manager/cert-manager#8232), [@eleanor-merry](https://github.com/eleanor-merry)) - Fix an issue where ACME challenge TXT records are not cleaned up when there are many resource records in CloudDNS. ([#8456](cert-manager/cert-manager#8456), [@tkna](https://github.com/tkna)) - Fix unregulated retries with the DigitalOcean DNS-01 solver Add full detailed DNS-01 errors to the events attached to the Challenge, for easier debugging ([#8221](cert-manager/cert-manager#8221), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. ([#8403](cert-manager/cert-manager#8403), [@calm329](https://github.com/calm329)) - Fixed an issue where HTTP-01 challenges failed when the Host header contains an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. ([#8424](cert-manager/cert-manager#8424), [@SlashNephy](https://github.com/SlashNephy)) - Fixed the HTTP-01 Gateway solver creating invalid HTTPRoutes by not setting spec.hostnames when the challenge DNSName is an IP address. ([#8443](cert-manager/cert-manager#8443), [@alviss7](https://github.com/alviss7)) - Revert API defaults for issuer reference kind and group introduced in 0.19.0 ([#8173](cert-manager/cert-manager#8173), [@erikgb](https://github.com/erikgb)) - Security (MODERATE): Fix a potential panic in the cert-manager controller when a DNS response in an unexpected order was cached. If an attacker was able to modify DNS responses (or if they controlled the DNS server) it was possible to cause denial of service for the cert-manager controller. ([#8469](cert-manager/cert-manager#8469), [@SgtCoDFish](https://github.com/SgtCoDFish)) - Update Go to `v1.25.5` to fix `CVE-2025-61727` and `CVE-2025-61729` ([#8290](cert-manager/cert-manager#8290), [@octo-sts](https://github.com/octo-sts)\[bot]) - When Prometheus monitoring is enabled, the metrics label is now set to the intended value of `cert-manager`. Previously, it was set depending on various factors (namespace cert-manager is installed in and/or Helm release name). ([#8162](cert-manager/cert-manager#8162), [@LiquidPL](https://github.com/LiquidPL)) ##### Other (Cleanup or Flake) - Promoted the OtherNames feature to Beta and enabled it by default ([#8288](cert-manager/cert-manager#8288), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Promoting `xlistenerset` feature gate to `listenerset` ([#8501](cert-manager/cert-manager#8501), [@hjoshi123](https://github.com/hjoshi123)) - Rebranding of the Venafi Issuer to CyberArk ([#8215](cert-manager/cert-manager#8215), [@iossifbenbassat123](https://github.com/iossifbenbassat123)) - Switched to SSA for challenge finalizer updates ([#8519](cert-manager/cert-manager#8519), [@inteon](https://github.com/inteon)) - The default container user (UID) is now 65532 (previously 1000) and the default container group (GID) is now 65532 (previously 0) ([#8408](cert-manager/cert-manager#8408), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - The feature-gate DefaultPrivateKeyRotationPolicyAlways moved from Beta to GA and can no longer be disabled. ([#8287](cert-manager/cert-manager#8287), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Update cert-manager's ACME client, forked from golang/x/crypto ([#8268](cert-manager/cert-manager#8268), [@SgtCoDFish](https://github.com/SgtCoDFish)) - Use the latest version of Kyverno (1.16.2) in the best-practice installation tests ([#8389](cert-manager/cert-manager#8389), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - We stopped testing with Coutour due to it not supporting the new XListenerSet resource, and moved to kgateway. ([#8426](cert-manager/cert-manager#8426), [@hjoshi123](https://github.com/hjoshi123)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://gitea.alexlebens.dev/alexlebens/infrastructure/pulls/4582 Co-authored-by: Renovate Bot <renovate-bot@alexlebens.net> Co-committed-by: Renovate Bot <renovate-bot@alexlebens.net>

cert-manager-prow bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 26, 2025

jcpunk force-pushed the networkPolicies branch from 322e411 to a8a69c1 Compare December 26, 2025 19:58

hjoshi123 requested changes Dec 27, 2025

View reviewed changes

deploy/charts/cert-manager/templates/networkpolicy-webhooks.yaml Outdated Show resolved Hide resolved

deploy/charts/cert-manager/templates/networkpolicy-webhooks.yaml Outdated Show resolved Hide resolved

deploy/charts/cert-manager/values.yaml Show resolved Hide resolved

jcpunk force-pushed the networkPolicies branch 2 times, most recently from 5736e7b to 5155f8f Compare December 29, 2025 14:47

cert-manager-prow bot added ok-to-test and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 29, 2025

jcpunk force-pushed the networkPolicies branch from 5155f8f to 348cd49 Compare December 29, 2025 16:45

avani8507 approved these changes Dec 30, 2025

View reviewed changes

cert-manager-prow bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 1, 2026

jcpunk force-pushed the networkPolicies branch from 348cd49 to 2408304 Compare January 2, 2026 17:30

cert-manager-prow bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 2, 2026

jcpunk force-pushed the networkPolicies branch from 2408304 to ce1fd1f Compare January 2, 2026 17:42

jcpunk requested a review from hjoshi123 January 2, 2026 17:56

cert-manager-prow bot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Jan 7, 2026

cert-manager-prow bot removed the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label Jan 7, 2026

maelvls requested a review from wallrj-cyberark January 9, 2026 11:05

wallrj-cyberark added the cybr Used by CyberArk-employed maintainers to report to line management what's being worked on. label Jan 9, 2026

wallrj-cyberark reviewed Jan 9, 2026

View reviewed changes

wallrj-cyberark mentioned this pull request Jan 9, 2026

Egress NetworkPolicy from Helm blocks kube-api traffic with Cilium #8285

Closed

feat(deploy/chart): optional networkPolicy for more containers

a0c521d

Fixes: cert-manager#8369 Signed-off-by: Pat Riehecky <riehecky@fnal.gov>

jcpunk force-pushed the networkPolicies branch from ce1fd1f to a0c521d Compare January 9, 2026 15:07

jcpunk requested a review from wallrj-cyberark January 9, 2026 15:10

wallrj-cyberark mentioned this pull request Jan 9, 2026

[VC-48226] Enable default NetworkPolicies in best-practice installation e2e tests #8387

Merged

wallrj-cyberark approved these changes Jan 16, 2026

View reviewed changes

wallrj-cyberark requested a review from wallrj January 16, 2026 14:39

cert-manager-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jan 16, 2026

cert-manager-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 16, 2026

wallrj-cyberark reviewed Jan 16, 2026

View reviewed changes

cert-manager-prow bot merged commit 4287874 into cert-manager:master Jan 16, 2026
6 checks passed

wallrj-cyberark mentioned this pull request Jan 16, 2026

[VC-48226]: document default NetworkPolicy and example values cert-manager/website#1911

Merged

jcpunk deleted the networkPolicies branch January 16, 2026 19:46

hjoshi123 mentioned this pull request Jan 31, 2026

adding hjoshi123 as approver #8462

Merged

github-actions bot mentioned this pull request Mar 30, 2026

Update Helm release cert-manager to v1.20.0 claytono/infra#1873

Merged

1 task

Conversation

jcpunk commented Dec 26, 2025 • edited by wallrj-cyberark Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pull Request Motivation

Kind

Release Note

Uh oh!

cert-manager-prow bot commented Dec 26, 2025

Uh oh!

hjoshi123 left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

jcpunk commented Dec 29, 2025

Uh oh!

hjoshi123 commented Dec 29, 2025

Uh oh!

jcpunk commented Dec 29, 2025

Uh oh!

jcpunk commented Dec 29, 2025

Uh oh!

erikgb commented Dec 29, 2025

Uh oh!

hjoshi123 commented Dec 31, 2025

Uh oh!

jcpunk commented Jan 2, 2026

Uh oh!

hjoshi123 commented Jan 7, 2026

Uh oh!

jcpunk commented Jan 7, 2026

Uh oh!

erikgb commented Jan 7, 2026

Uh oh!

jcpunk commented Jan 7, 2026

Uh oh!

wallrj-cyberark left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

wallrj-cyberark left a comment

Choose a reason for hiding this comment

Uh oh!

wallrj commented Jan 16, 2026

Uh oh!

cert-manager-prow bot commented Jan 16, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

wallrj-cyberark commented Jan 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

wallrj-cyberark commented Feb 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

jcpunk commented Dec 26, 2025 •

edited by wallrj-cyberark

Loading

hjoshi123 left a comment •

edited

Loading

wallrj-cyberark commented Jan 16, 2026 •

edited

Loading