-
Notifications
You must be signed in to change notification settings - Fork 375
Release notes for cert-manager v1.19.0 #1792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release notes for cert-manager v1.19.0 #1792
Conversation
- Populate release-notes-1.19.md with major themes and highlights - Add categorized changes sections: Feature, Bug or Regression, Other - Add contributor acknowledgements and notes about upgrades and fixes Signed-off-by: Richard Wall <richard.wall@cyberark.com>
✅ Deploy Preview for cert-manager ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: Richard Wall <richard.wall@cyberark.com>
Signed-off-by: Richard Wall <richard.wall@cyberark.com>
Signed-off-by: Richard Wall <richard.wall@cyberark.com>
Signed-off-by: Richard Wall <richard.wall@cyberark.com>
Signed-off-by: Richard Wall <richard.wall@cyberark.com>
Signed-off-by: Richard Wall <richard.wall@cyberark.com>
| </td> | ||
| <td> | ||
| <p>The IP address or hostname of an authoritative DNS server supporting RFC2136 in the form host:port. If the host is an IPv6 address it must be enclosed in square brackets (e.g [2001:db8::1]) ; port is optional. This field is required.</p> | ||
| <p>The IP address or hostname of an authoritative DNS server supporting RFC2136 in the form host:port. If the host is an IPv6 address it must be enclosed in square brackets (e.g [2001:db8::1]); port is optional. This field is required.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a weird whitespace character here which I had to manually delete. It was being picked up by eslint:
But it seems to be added at least 5 years ago:
|
|
||
| - TODO | ||
|
|
||
| {/* BEGIN contributors */} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These template variables are used by a new cert-manager-release-notes tool that I'm developing in:
| | Release | Release Date | End of Life | [Supported Kubernetes / OpenShift Versions][s] | [Tested Kubernetes Versions][test] | | ||
| |:--------:|:------------:|:---------------:|:----------------------------------------------:|:----------------------------------:| | ||
| | [1.19][] | Oct 7, 2025 | Release of 1.21 | 1.31 → 1.34 / 4.18 → 4.19 | 1.31 → 1.34 | | ||
| | [1.20][] | Feb 10, 2026 | Release of 1.21 | 1.31 → 1.34 / 4.18 → 4.19 | 1.31 → 1.34 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The first Tuesday, four months from October 7, 2025.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! I've left 2 minor comments. Feel free to unhold.
/hold
/lgtm
| --- | ||
|
|
||
| Before upgrading cert-manager from 1.18 to 1.19, please read the following important notes about breaking changes in 1.19: | ||
| Before upgrading cert-manager from 1.18 to 1.19, please read the following important notes about breaking changes in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Before upgrading cert-manager from 1.18 to 1.19, please read the following important notes about breaking changes in | |
| Before upgrading cert-manager from 1.18 to 1.19, please read the following important notes about breaking changes: |
| <em> | ||
| <a href="#meta.cert-manager.io/v1.ObjectReference">ObjectReference</a> | ||
| </em> | ||
| <em>github.com/cert-manager/cert-manager/pkg/apis/meta/v1.IssuerReference</em> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll investigate that in another PR.
|
|
||
| ### Observability, Reliability, and Maintenance | ||
| - There is a new Prometheus metric called `certmanager_certificate_challenge_status`. | ||
| - POTENTIALLY BREAKING: A high cardinality label, called `path`, was removed from the `certmanager_acme_client_request_count` and `certmanager_acme_client_request_duration_seconds` metrics. It is replaced with a new bounded cardinality label called `action`. This may require updates to dashboards and alerts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: It would be good to show an example before/after, but I guess users can open the corresponding issue, which might already contain an example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree. But I'm running out of time to get this merged before EOD. I'll revisit in another PR.
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: maelvls, wallrj The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/unhold |
342db6a
into
cert-manager:release-next

Preview:
Part of: cert-manager/cert-manager#8113
These changes were carried out according to the release-notes sections of the release process:
I used the cert-manager release-notes tool that I'm developing in #1785 and added some narrative with the help of gpt-5-mini.
The changes will be merged into the
release-nextbranch, which will later be merged into the main branch when we've published the release.