Skip to content

feat(container): update image trust-manager ( v0.22.1 → v0.24.0 )#3376

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/trust-manager-0.x
Open

feat(container): update image trust-manager ( v0.22.1 → v0.24.0 )#3376
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/trust-manager-0.x

Conversation

@renovate

@renovate renovate Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
trust-manager (source) minor v0.22.1v0.24.0

Release Notes

cert-manager/trust-manager (trust-manager)

v0.24.0

Compare Source

trust-manager is the easiest way to manage security-critical TLS trust bundles in Kubernetes and OpenShift clusters.

This release is a feature release, but as usual, it contains various patches/fixes and dependency bumps.

Notable changes include a fix by @​yugstar avoiding reconciling loops by ensuring the calculated trust bundle hash is deterministic when adding labels/annotations to the target configmaps/secrets. 💯 And trust-manager can now source CA certificates from configmap binaryData. 🚀

Our Helm chart now supports configuration of securityContexts for pods and containers, which has been highly requested by the community. A big thanks goes out to @​MarcAntoineRaymond! ❤️

⚠️ Possibly breaking change in Helm chart values: if you currently set app.securityContext.seccompProfileEnabled, this value has been removed and replaced with a more generic mechanism for setting securityContexts.

What's Changed
Features
Fixes
Bumps / CI
New Contributors

Full Changelog: cert-manager/trust-manager@v0.23.0...v0.24.0

v0.24.0

Compare Source

trust-manager is the easiest way to manage security-critical TLS trust bundles in Kubernetes and OpenShift clusters.

This release is a feature release, but as usual, it contains various patches/fixes and dependency bumps.

Notable changes include a fix by @​yugstar avoiding reconciling loops by ensuring the calculated trust bundle hash is deterministic when adding labels/annotations to the target configmaps/secrets. 💯 And trust-manager can now source CA certificates from configmap binaryData. 🚀

Our Helm chart now supports configuration of securityContexts for pods and containers, which has been highly requested by the community. A big thanks goes out to @​MarcAntoineRaymond! ❤️

⚠️ Possibly breaking change in Helm chart values: if you currently set app.securityContext.seccompProfileEnabled, this value has been removed and replaced with a more generic mechanism for setting securityContexts.

What's Changed
Features
Fixes
Bumps / CI
New Contributors

Full Changelog: cert-manager/trust-manager@v0.23.0...v0.24.0

v0.23.0

Compare Source

trust-manager is the easiest way to manage security-critical TLS trust bundles in Kubernetes and OpenShift clusters.

This release is a feature release, but as usual, it contains various patches/fixes and dependency bumps.

The most notable feature in this release is probably that trust-manager now provides a new trust-package bundle based on Debian Trixie.
💡 Note that the new trust-pkg-debian-trixie bundle is now the default trust package emitted by the Helm chart. For those of you still using our trust packages built from Debian Bullseye/Bookworm, we've just published new releases to fix vulnerabilites reported by scanners.

Our Helm chart has a new feature that allows a user to override the default webhook TLS certificate duration. We've also got a fix making it easier to use the trust-manager chart in an umbrella chart together with other cert-manager projects. This release also includes multiple fixes/inconsistencies in the Helm chart when using non-default values.

What's Changed

Features
Fixes
Bumps / CI

New Contributors

Full Changelog: cert-manager/trust-manager@v0.22.1...v0.23.0

v0.23.0

Compare Source

trust-manager is the easiest way to manage security-critical TLS trust bundles in Kubernetes and OpenShift clusters.

This release is a feature release, but as usual, it contains various patches/fixes and dependency bumps.

The most notable feature in this release is probably that trust-manager now provides a new trust-package bundle based on Debian Trixie.
💡 Note that the new trust-pkg-debian-trixie bundle is now the default trust package emitted by the Helm chart. For those of you still using our trust packages built from Debian Bullseye/Bookworm, we've just published new releases to fix vulnerabilites reported by scanners.

Our Helm chart has a new feature that allows a user to override the default webhook TLS certificate duration. We've also got a fix making it easier to use the trust-manager chart in an umbrella chart together with other cert-manager projects. This release also includes multiple fixes/inconsistencies in the Helm chart when using non-default values.

What's Changed

Features
Fixes
Bumps / CI

New Contributors

Full Changelog: cert-manager/trust-manager@v0.22.1...v0.23.0


Configuration

📅 Schedule: (in timezone America/Chicago)

  • 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 becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

@github-actions

github-actions Bot commented Jun 10, 2026

Copy link
Copy Markdown

Path: infrastructure/trust-manager
Version: v0.22.1 -> v0.24.0

--- /tmp/tmp.9vUDftRbjY	2026-07-20 20:42:17.259087881 +0000
+++ /tmp/tmp.hMbbnEjfcJ	2026-07-20 20:42:18.035085800 +0000
@@ -535,6 +535,23 @@
         status: {}
 
 ---
+# Source: trust-manager/charts/trust-manager/templates/clusterrole-aggregate.yaml
+# Bundle is a cluster-scoped resource, so its read access is aggregated into
+# the "cluster-reader" ClusterRole (mirroring how cert-manager aggregates its
+# cluster-scoped ClusterIssuers), rather than into the namespaced
+# view/edit/admin roles.
+kind: ClusterRole
+apiVersion: rbac.authorization.k8s.io/v1
+metadata:
+  name: trust-manager-cluster-view
+rules:
+  - apiGroups:
+      - "trust.cert-manager.io"
+    resources:
+      - "bundles"
+    verbs: [ "get", "list", "watch" ]
+
+---
 # Source: trust-manager/charts/trust-manager/templates/clusterrole.yaml
 kind: ClusterRole
 apiVersion: rbac.authorization.k8s.io/v1
@@ -716,7 +733,7 @@
       automountServiceAccountToken: true
       initContainers:
         - name: cert-manager-package-debian
-          image: "quay.io/jetstack/trust-pkg-debian-bookworm:20230311-deb12u1.6"
+          image: "quay.io/jetstack/trust-pkg-debian-trixie:20250419.1"
           imagePullPolicy: IfNotPresent
           args:
             - "/copyandmaybepause"
@@ -737,7 +754,7 @@
               type: RuntimeDefault
       containers:
         - name: trust-manager
-          image: "quay.io/jetstack/trust-manager:v0.22.1"
+          image: "quay.io/jetstack/trust-manager:v0.24.0"
           imagePullPolicy: IfNotPresent
           ports:
             - containerPort: 6443

@renovate
renovate Bot force-pushed the renovate/trust-manager-0.x branch from 0b75a8c to 205e903 Compare June 18, 2026 17:45
@renovate
renovate Bot force-pushed the renovate/trust-manager-0.x branch from 205e903 to efd61b4 Compare June 27, 2026 17:42
@renovate renovate Bot changed the title feat(container): update image trust-manager ( v0.22.1 → v0.23.0 ) feat(container): update image trust-manager ( v0.22.1 → v0.24.0 ) Jun 27, 2026
| datasource | package                               | from    | to      |
| ---------- | ------------------------------------- | ------- | ------- |
| docker     | quay.io/jetstack/charts/trust-manager | v0.22.1 | v0.24.0 |


Signed-off-by: Roger Rumao <rogerrum@users.noreply.github.com>
@renovate
renovate Bot force-pushed the renovate/trust-manager-0.x branch from efd61b4 to 74104a1 Compare July 20, 2026 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants