mirror of
https://ghproxy.com/https://github.com/truecharts/charts.git
synced 2026-02-02 23:03:17 +08:00
b258f943af
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [cert-manager](https://cert-manager.io) ([source](https://redirect.github.com/cert-manager/cert-manager)) | minor | `v1.16.3` -> `v1.17.0` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>cert-manager/cert-manager (cert-manager)</summary> ### [`v1.17.0`](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.17.0) [Compare Source](https://redirect.github.com/cert-manager/cert-manager/compare/v1.16.3...v1.17.0) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.17.0 is a feature release with several improvements, including: - A helpful compliance change to RSA signatures on certificates - An easier way to specify passwords for [PKCS#12](https://redirect.github.com/PKCS/cert-manager/issues/12) and JKS keystores - A few feature flag promotions (and a deprecation) - Dependency bumps and other smaller improvements #### Major Themes ##### RSA Certificate Compliance The United States Department of Defense published [a memo](https://dl.dod.cyber.mil/wp-content/uploads/pki-pke/pdf/unclass-memo_dodcryptoalgorithms.pdf) in 2022 which introduced some requirements on the kinds of cryptography they require to be supported in software they use. In effect, the memo requires that software be able to support larger RSA keys (3072-bit and 4096-bit) and hashing algorithms (SHA-384 at a minimum). cert-manager supported large RSA keys long before the memo was published, but a quirk in implementation meant that cert-manager always used SHA-256 when signing with RSA. In v1.17.0, cert-manager will choose a hash algorithm based on the RSA key length: 3072-bit keys will use SHA-384, and 4096-bit keys will use SHA-512. This matches similar behavior already present for ECDSA signatures. Our expectation is that this change will have minimal impact beyond a slight increase to security and better compliance; we're not aware of Kubernetes based environments which support RSA 2048 with SHA-256 but fail with RSA 4096 and SHA-512. However, if you're using larger RSA keys, you should be aware of the change. ##### Easier Keystore Passwords for [PKCS#12](https://redirect.github.com/PKCS/cert-manager/issues/12) and JKS Specifying passwords on [PKCS#12](https://redirect.github.com/PKCS/cert-manager/issues/12) and JKS keystores is supported in cert-manager for compatibility reasons with software which expects or requires passwords to be set; however, these passwords are [not relevant to security](https://cert-manager.io/docs/faq/#why-are-passwords-on-jks-or-pkcs12-files-not-helpful) and never have been in cert-manager. The initial implementation of the `keystores` feature required these "passwords" to be stored in a Kubernetes secret, which would then be read by cert-manager when creating the keystore after a certificate was issued. This is cumbersome, especially when many passwords are set to default values such as `changeit` or `password`. In cert-manager v1.17, it's now possible to set a keystore password using a literal string value inside the `Certificate` resource itself, making this process much easier with no change to security. For example: ```yaml apiVersion: cert-manager.io/v1 kind: Certificate metadata: name: my-cert-password spec: secretName: my-cert-password issuerRef: name: my-issuer kind: ClusterIssuer keystores: jks: create: true password: "abc123" pkcs12: create: true password: "password" dnsNames: - example.com ``` The new `password` field is mutually exclusive with the `passwordSecretRef` field, so be sure to only set one. ##### Feature Flag Promotions / Deprecations cert-manager's feature flags allow for easier testing and adoption of new features with a reduced risk of breaking changes. In cert-manager v1.17, two feature gates have been promoted to "beta", and as such are now enabled by default in all installations: - `NameConstraints`, allowing users to specify the name constraints extension which can be helpful when creating CA certificates for private PKI - `UseDomainQualifiedFinalizer`, which stops a Kubernetes warning from being printed in logs In addition, we added a new feature gate: `CAInjectorMerging`, which intelligently combines certificates used by the [`CAInjector`](../../concepts/ca-injector.md) component, making it safer to use when issuing certificates are rotated. If you're making heavy use of the CA injector, you should consider enabling this feature gate. Finally, we deprecated the `ValidateCAA` feature gate which will be removed entirely in cert-manager v1.18.0. This feature gate aimed to validate the `CAA` DNS record during ACME issuance, but has seen low adoption and limited testing since its introduction back in 2019. ##### Other Changes There are many other PRs which were merged in this release cycle and we'd encourage you to read the release notes below. One PR that's worth highlighting is a change to add more structured logging information to certain log lines. If you were previously filtering logs using `grep` or similar tools (which is highly discouraged!) be aware that some log lines have changed format. #### Community As always, we'd like to thank all of the community members who helped in this release cycle, including all below who merged a PR and anyone that helped by commenting on issues, testing, or getting involved in cert-manager meetings. We're lucky to have you involved. A special thanks to: - [@​hawksight](https://redirect.github.com/hawksight) - [@​aidy](https://redirect.github.com/aidy) - [@​bashlion](https://redirect.github.com/bashlion) - [@​7ing](https://redirect.github.com/7ing) - [@​fadecore](https://redirect.github.com/fadecore) - [@​schedin](https://redirect.github.com/schedin) - [@​jkroepke](https://redirect.github.com/jkroepke) - [@​sdarwin](https://redirect.github.com/sdarwin) for their contributions, comments and support! Also, thanks to the cert-manager maintainer team for their help in this release: - [@​inteon](https://redirect.github.com/inteon) - [@​erikgb](https://redirect.github.com/erikgb) - [@​SgtCoDFish](https://redirect.github.com/SgtCoDFish) - [@​ThatsMrTalbot](https://redirect.github.com/ThatsMrTalbot) - [@​munnerz](https://redirect.github.com/munnerz) - [@​maelvls](https://redirect.github.com/maelvls) And finally, thanks to the cert-manager steering committee for their feedback in this release cycle: - [@​FlorianLiebhart](https://redirect.github.com/FlorianLiebhart) - [@​ssyno](https://redirect.github.com/ssyno) - [@​ianarsenault](https://redirect.github.com/ianarsenault) - [@​TrilokGeer](https://redirect.github.com/TrilokGeer) #### Changes by Kind ##### Feature - Potentially BREAKING: The CA and SelfSigned issuers now use SHA-512 when signing with RSA keys 4096 bits and above, and SHA-384 when signing with RSA keys 3072 bits and above. If you were previously using a larger RSA key as a CA, be sure to check that your systems support the new hash algorithms. ([#​7368](https://redirect.github.com/cert-manager/cert-manager/issues/7368), [@​SgtCoDFish](https://redirect.github.com/SgtCoDFish)) - Add CAInjectorMerging feature gate to the ca-injector, enabling this will change the behaviour of the ca-injector to merge in new CA certificates instead of outright replacing the existing one. ([#​7469](https://redirect.github.com/cert-manager/cert-manager/issues/7469), [@​ThatsMrTalbot](https://redirect.github.com/ThatsMrTalbot)) - Added image pull secrets to deployments when service accounts aren't created ([#​7411](https://redirect.github.com/cert-manager/cert-manager/issues/7411), [@​TheHenrick](https://redirect.github.com/TheHenrick)) - Added the ability to customize client ID when using username/password authentication for Venafi client ([#​7484](https://redirect.github.com/cert-manager/cert-manager/issues/7484), [@​ilyesAj](https://redirect.github.com/ilyesAj)) - Helm: New value `webhook.extraEnv` allows you to set custom environment variables in the webhook Pod. Helm: New value `cainjector.extraEnv` allows you to set custom environment variables in the cainjector Pod. Helm: New value `startupapicheck.extraEnv` allows you to set custom environment variables in the startupapicheck Pod. ([#​7317](https://redirect.github.com/cert-manager/cert-manager/issues/7317), [@​wallrj](https://redirect.github.com/wallrj)) - Increase the amount of PEM data `pki.DecodeX509CertificateSetBytes` is able to parse, to enable reading larger TLS trust bundles ([#​7464](https://redirect.github.com/cert-manager/cert-manager/issues/7464), [@​SgtCoDFish](https://redirect.github.com/SgtCoDFish)) - New configuration option tenantID for the AzureDNS provider when using managed identities with service principals. This enhancement allows users to specify the tenant ID when using managed identities, offering better flexibility in multi-tenant environments. ([#​7376](https://redirect.github.com/cert-manager/cert-manager/issues/7376), [@​jochenrichter](https://redirect.github.com/jochenrichter)) - Promote the `UseDomainQualifiedFinalizer` feature to Beta. ([#​7488](https://redirect.github.com/cert-manager/cert-manager/issues/7488), [@​jsoref](https://redirect.github.com/jsoref)) - Allow JKS/PKCS12 keystore passwords to be set as literal values in Certificate resources, mutually exclusive with the existing passwordSecretRef field ([#​6657](https://redirect.github.com/cert-manager/cert-manager/issues/6657), [@​rquinio1A](https://redirect.github.com/rquinio1A)) - Allow templating ServiceAccount annotations by running the built-in Helm `tpl` function on keys and values, to aid with workload identity configuration ([#​7501](https://redirect.github.com/cert-manager/cert-manager/issues/7501), [@​fcrespofastly](https://redirect.github.com/fcrespofastly)) - Promote CA NameConstraints feature gate to Beta (enabled by default) ([#​7494](https://redirect.github.com/cert-manager/cert-manager/issues/7494), [@​tanujd11](https://redirect.github.com/tanujd11)) ##### Documentation - Add example for IPv6 in `--dns01-recursive-nameservers` ([#​7367](https://redirect.github.com/cert-manager/cert-manager/issues/7367), [@​SgtCoDFish](https://redirect.github.com/SgtCoDFish)) - Updated the chart documentation to show `enableGatewayAPI` in the config example. ([#​7354](https://redirect.github.com/cert-manager/cert-manager/issues/7354), [@​puerco](https://redirect.github.com/puerco)) ##### Bug or Regression - BUGFIX: A change in v1.16.0 caused cert-manager's ACME ClusterIssuer to look in the wrong namespace for resources required for the issuance (eg. credential Secrets). This is now fixed in v1.16.1+ and v1.17.0+ ([#​7339](https://redirect.github.com/cert-manager/cert-manager/issues/7339), [@​inteon](https://redirect.github.com/inteon)) - BUGFIX: Helm will now accept percentages for the `podDisruptionBudget.minAvailable` and `podDisruptionBudget.maxAvailable` values. ([#​7343](https://redirect.github.com/cert-manager/cert-manager/issues/7343), [@​inteon](https://redirect.github.com/inteon)) - Fix ACME HTTP-01 solver for IPv6 endpoints ([#​7391](https://redirect.github.com/cert-manager/cert-manager/issues/7391), [@​Peac36](https://redirect.github.com/Peac36)) - Fix the behavior of `renewBeforePercentage` to comply with its spec ([#​7421](https://redirect.github.com/cert-manager/cert-manager/issues/7421), [@​adam-sroka](https://redirect.github.com/adam-sroka)) - Helm: allow `enabled` to be set as a value to toggle cert-manager as a dependency. ([#​7350](https://redirect.github.com/cert-manager/cert-manager/issues/7350), [@​inteon](https://redirect.github.com/inteon)) - SECURITY (low risk): Limit maximum allowed PEM size to prevent potential DoS in cert-manager controller from attacker-controlled PEM. See [GHSA-r4pg-vg54-wxx4](https://redirect.github.com/cert-manager/cert-manager/security/advisories/GHSA-r4pg-vg54-wxx4) ([#​7400](https://redirect.github.com/cert-manager/cert-manager/issues/7400), [@​SgtCoDFish](https://redirect.github.com/SgtCoDFish)) - The Certificate object will no longer create CertificateRequest or Secret objects while being deleted ([#​7361](https://redirect.github.com/cert-manager/cert-manager/issues/7361), [@​ThatsMrTalbot](https://redirect.github.com/ThatsMrTalbot)) - The issuer will now more quickly retry when its linked Secret is updated to fix an issue that caused a high back-off timeout. ([#​7455](https://redirect.github.com/cert-manager/cert-manager/issues/7455), [@​inteon](https://redirect.github.com/inteon)) - Upgrades Venafi vCert library fixing a bug which caused the RSA 3072 bit key size for TPP certificate enrollment to not work. ([#​7498](https://redirect.github.com/cert-manager/cert-manager/issues/7498), [@​inteon](https://redirect.github.com/inteon)) ##### Other (Cleanup or Flake) - ⚠️ Potentially BREAKING: Log messages that were not structured have now been replaced with structured logs. If you were matching on specific log strings, this could break your setup. ([#​7461](https://redirect.github.com/cert-manager/cert-manager/issues/7461), [@​inteon](https://redirect.github.com/inteon)) - DEPRECATION: The `ValidateCAA` feature gate is now deprecated, with removal scheduled for cert-manager 1.18. In 1.17, enabling this feature gate will print a warning. ([#​7491](https://redirect.github.com/cert-manager/cert-manager/issues/7491), [@​jsoref](https://redirect.github.com/jsoref)) - Remove `Neither --kubeconfig nor --master was specified` warning message when the controller and the webhook services boot ([#​7457](https://redirect.github.com/cert-manager/cert-manager/issues/7457), [@​Peac36](https://redirect.github.com/Peac36)) - Move 'live' DNS tests into a separate package to contain test flakiness and improve developer UX ([#​7530](https://redirect.github.com/cert-manager/cert-manager/issues/7530), [@​SgtCoDFish](https://redirect.github.com/SgtCoDFish)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS44Ni4xIiwidXBkYXRlZEluVmVyIjoiMzkuODYuMSIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6WyJhdXRvbWVyZ2UiLCJyZW5vdmF0ZS9jb250YWluZXIiLCJyZW5vdmF0ZS9oZWxtIiwidHlwZS9taW5vciJdfQ==--> --------- Signed-off-by: Alfred Göppel <43101280+alfi0812@users.noreply.github.com> Co-authored-by: Alfred Göppel <43101280+alfi0812@users.noreply.github.com>
title
| title |
|---|
| TrueCharts |
Community Helm Chart Catalog
TrueCharts is a catalog of highly optimised Helm Charts. Made for the community, By the community!
All our charts are supposed to work together and be easy to setup using any helm-compatible deployment tool, above all, give the average user more than enough options to tune things to their liking.
Getting started using TrueCharts
Support
Please check our FAQ, manual and Issue tracker There is a significant chance your issue has been reported before!
Still something not working as expected? Contact us! and we'll figure it out together!
Development
Our development process is fully distributed and agile, so every chart-maintainer is free to set their own roadmap and development speed and does not have to comply to a centralised roadmap. This ensures freedom and flexibility for everyone involved and makes sure you, the end user, always has the latest and greatest of every Chart installed.
Getting into creating Charts
For more information check the website: https://truecharts.org
Contact and Support
To contact the TrueCharts project:
-
Create an issue on Github issues
-
Open a Support Ticket
-
Send us an email
Contributors ✨
Thanks goes to these wonderful people (emoji key):
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?v=4?s=100)
![allcontributors[bot]](https://avatars.githubusercontent.com/in/23186?v=4?s=100)
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4?s=100)
This project follows the all-contributors specification. Contributions of any kind welcome!
Licence
Truecharts, is primarily based on a AGPL-v3 license, this ensures almost everyone can use and modify our charts. Licences can vary on a per-Chart basis. This can easily be seen by the presence of a "LICENSE" file in said folder.
An exception to this, has been made for every document inside folders labeled as docs or doc and their subfolders: those folders are not licensed under AGPL-v3 and are considered "all rights reserved". Said content can be modified and changes submitted per PR, in accordance to the github End User License Agreement.
SPDX-License-Identifier: AGPL-3.0
