Update Helm release trust-manager to v0.15.0 #97
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.12.0->0.15.0Release Notes
cert-manager/trust-manager (trust-manager)
v0.15.0Compare Source
trust-manager is the easiest way to manage security-critical TLS trust bundles in Kubernetes and OpenShift clusters.
The most important changes in this release are a slew of version bumps, with some important consequences for how trust-manager parses certificates.
trust-manager v0.15.0 uses Go 1.23, which by default disallows parsing of certificates with negative serial numbers. Most certificates are unaffected by this, since a negative serial number would be in violation of relevant standards and specs.
Unfortunately, some legacy certificates are not compliant, and there are certificates in the wild with negative serial numbers including one certificate which appears in the trust-manager default trust package (since it was included in Debian 10).
We've decided to make this certificate a special case and ignore it when it's included in a bundle. While it's still present in the trust package container image it will be ignored when the
cert-manager-package-debian:20210119.0package is used or if manually included. When it's ignored, a log line will be emitted each time:time=2025-01-13T11:37:10.034Z level=INFO msg="skipping a certificate in PEM bundle for compatibility reasons" logger=trust/bundle/cert-pool details="cert in bundle with CN=EC-ACC and fingerprint '88497f01602f3154246ae28c4d5aef10f1d87ebb76626f4ae0b7f95ba7968799' has negative serial number and will be skipped"If you depend on trusting certs with negative serial numbers, support for them can be re-enabled at runtime by setting the
GODEBUGenvironment variable tox509negativeserial=1in the trust-manager container:If this value is not set - which is the default behavior - all certs with negative serial numbers will cause an error on the bundle except for the special case certificate above, which will be skipped.
What's Changed
Important Changes
Makefile Modules Bumps, Fixes and Tweaks
Dependency Bumps / Miscellaneous Changes
Full Changelog: cert-manager/trust-manager@v0.14.0...v0.15.0
v0.14.0Compare Source
trust-manager is the easiest way to manage security-critical TLS trust bundles in Kubernetes and OpenShift clusters.
v0.14.0 is a minor release including new features, some bugfixes, refactors and dependency updates.
Among the new features is support for set-based requirements (
matchExpressions) when selecting namepaces to target with aBundle.This release also inludes some major bugfixes:
keyto be omitted when using the newincludeAllKeysfield introduced in v0.13.0 by @juliocamarero.Thanks to all contributors! 🚀
New features
Bugfixes
Enhancements and Refactorings
Automated Dependency Bumps
Automated Makefile Modules Updates
New Contributors
Full Changelog: cert-manager/trust-manager@v0.13.0...v0.14.0
v0.13.0Compare Source
trust-manager is the easiest way to manage security-critical TLS trust bundles in Kubernetes and OpenShift clusters.
v0.13.0 is a minor release to include a swathe of dependency updates, refactors and a few new features.
Among the new features is the new optional
includeAllKeysfield forSecretandConfigMapsources, by @juliocamarero. Previously, these sources required users to specify an indvidual key to include in the resulting bundle. With this new field, you can request that all keys be included instead. Note that Secret sources ofkubernetes.io/tlstype are not eligible for use withincludeAllKeys, to avoid trust-manager reading a private key.In addition, @arsenalzp landed a great PR which cleans up handling of certificates within trust-manager, reducing the number of encode/decode operations done during a bundle reconcile.
What's Changed
Refactoring
Automated Dependency Bumps
Automated Makefile Modules Updates
New Contributors
Full Changelog: cert-manager/trust-manager@v0.12.0...v0.13.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.