deps: bump cert-manager Helm chart to v1.17.1 #1006
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
updatecli_master_certmanager
branch
from
de28e0a to
fc15e66
Compare
github-actions
bot
changed the title
github-actions
bot
changed the title
github-actions
bot
force-pushed
the
updatecli_master_certmanager
branch
2 times, most recently
from
8f3a821 to
a35401c
Compare
Made with ❤️️ by updatecli
github-actions
bot
force-pushed
the
updatecli_master_certmanager
branch
from
3ff6584 to
d2651c7
Compare
Made with ❤️️ by updatecli
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.
deps: bump cert-manager version
Update cert-manager/manifest.yaml
change detected: * key "$.version" updated from "v1.16.2" to "v1.17.1", in file "cert-manager/manifest.yaml"
v1.17.1
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 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 and JKS Specifying passwords on PKCS#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 - @aidy - @bashlion - @7ing - @fadecore - @schedin - @jkroepke - @sdarwin for their contributions, comments and support! Also, thanks to the cert-manager maintainer team for their help in this release: - @inteon - @erikgb - @SgtCoDFish - @ThatsMrTalbot - @munnerz - @maelvls And finally, thanks to the cert-manager steering committee for their feedback in this release cycle: - @FlorianLiebhart - @ssyno - @ianarsenault - @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, @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, @ThatsMrTalbot) - Added image pull secrets to deployments when service accounts aren't created (#7411, @TheHenrick) - Added the ability to customize client ID when using username/password authentication for Venafi client (#7484, @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, @wallrj) - Increase the amount of PEM data `pki.DecodeX509CertificateSetBytes` is able to parse, to enable reading larger TLS trust bundles (#7464, @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, @jochenrichter) - Promote the `UseDomainQualifiedFinalizer` feature to Beta. (#7488, @jsoref) - Allow JKS/PKCS12 keystore passwords to be set as literal values in Certificate resources, mutually exclusive with the existing passwordSecretRef field (#6657, @rquinio1A) - Allow templating ServiceAccount annotations by running the built-in Helm `tpl` function on keys and values, to aid with workload identity configuration (#7501, @fcrespofastly) - Promote CA NameConstraints feature gate to Beta (enabled by default) (#7494, @tanujd11) ### Documentation - Add example for IPv6 in `--dns01-recursive-nameservers` (#7367, @SgtCoDFish) - Updated the chart documentation to show `enableGatewayAPI` in the config example. (#7354, @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, @inteon) - BUGFIX: Helm will now accept percentages for the `podDisruptionBudget.minAvailable` and `podDisruptionBudget.maxAvailable` values. (#7343, @inteon) - Fix ACME HTTP-01 solver for IPv6 endpoints (#7391, @Peac36) - Fix the behavior of `renewBeforePercentage` to comply with its spec (#7421, @adam-sroka) - Helm: allow `enabled` to be set as a value to toggle cert-manager as a dependency. (#7350, @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://github.com/cert-manager/cert-manager/security/advisories/GHSA-r4pg-vg54-wxx4) (#7400, @SgtCoDFish) - The Certificate object will no longer create CertificateRequest or Secret objects while being deleted (#7361, @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, @inteon) - Upgrades Venafi vCert library fixing a bug which caused the RSA 3072 bit key size for TPP certificate enrollment to not work. (#7498, @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, @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, @jsoref) - Remove `Neither --kubeconfig nor --master was specified` warning message when the controller and the webhook services boot (#7457, @Peac36) - Move 'live' DNS tests into a separate package to contain test flakiness and improve developer UX (#7530, @SgtCoDFish)v1.17.0-beta.0
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.17.0 is a minor feature release including several improvements. Please help the project by testing this release! cert-manager v1.17 includes: - A helpful compliance change to RSA signatures on certificates - An easier way to specify passwords for PKCS#12 and JKS keystores - 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 SHA256 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 / SHA-256 but fail with RSA 4096 / SHA-512. However, if you're using larger RSA keys you should be aware of the change. ### Easier Keystore Passwords for PKCS#12 and JKS Specifying passwords on PKCS#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](../../faq/README.md##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, and especially so 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 - @aidy - @bashlion - @7ing - @fadecore - @schedin - @jkroepke for their contributions, comments and support! Also, thanks to the cert-manager maintainer team for their help in this release: - @inteon - @erikgb - @SgtCoDFish - @ThatsMrTalbot - @munnerz - @maelvls And finally, thanks to the cert-manager steering committee for their feedback in this release cycle: - @FlorianLiebhart - @ssyno - @ianarsenault - @TrilokGeer ## Changes by Kind ### Feature - Potentially BREAKING: The CA and SelfSigned issuers now use SHA512 when signing with RSA keys 4096 bits and above, and SHA384 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, @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, @ThatsMrTalbot) - Added image pull secrets to deployments when service accounts aren't created (#7411, @TheHenrick) - Added the ability to customize client ID when using username/password authentication for Venafi client (#7484, @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, @wallrj) - Increase the amount of PEM data `pki.DecodeX509CertificateSetBytes` is able to parse, to enable reading larger TLS trust bundles (#7464, @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, @jochenrichter) - Promote the `UseDomainQualifiedFinalizer` feature to Beta. (#7488, @jsoref) - Allow JKS/PKCS12 keystore passwords to be set as literal values in Certificate resources, mutually exclusive with the existing passwordSecretRef field (#6657, @rquinio1A) - Allow templating ServiceAccount annotations by running the built-in Helm `tpl` function on keys and values, to aid with workload identity configuration (#7501, @fcrespofastly) - Promote CA NameConstraints feature gate to Beta (enabled by default) (#7494, @tanujd11) ### Documentation - Add example for IPv6 in `--dns01-recursive-nameservers` (#7367, @SgtCoDFish) - Updated the chart documentation to show `enableGatewayAPI` in the config example. (#7354, @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, @inteon) - BUGFIX: Helm will now accept percentages for the `podDisruptionBudget.minAvailable` and `podDisruptionBudget.maxAvailable` values. (#7343, @inteon) - Fix ACME HTTP-01 solver for IPv6 endpoints (#7391, @Peac36) - Fix the behavior of `renewBeforePercentage` to comply with its spec (#7421, @adam-sroka) - Helm: allow `enabled` to be set as a value to toggle cert-manager as a dependency. (#7350, @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://github.com/cert-manager/cert-manager/security/advisories/GHSA-r4pg-vg54-wxx4) (#7400, @SgtCoDFish) - The Certificate object will no longer create CertificateRequest or Secret objects while being deleted (#7361, @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, @inteon) - Upgrades Venafi vCert library fixing a bug which caused the RSA 3072 bit key size for TPP certificate enrollment to not work. (#7498, @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, @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, @jsoref) - Remove `Neither --kubeconfig nor --master was specified` warning message when the controller and the webhook services boot (#7457, @Peac36) - Move 'live' DNS tests into a separate package to contain test flakiness and improve developer UX (#7530, @SgtCoDFish)v1.17.0-alpha.0
v1.16.4
v1.16.3
v1.16.2
Update cert-manager/install.sh
1 file(s) updated with "/download/v1.17.1/": * cert-manager/install.sh
v1.17.1
Created automatically by Updatecli
Options:
Most of Updatecli configuration is done via its manifest(s).
Feel free to report any issues at github.com/updatecli/updatecli.
If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!