Skip to content

Remove outdated information regarding Let's Encrypt ACME client behavior#1916

Merged
cert-manager-prow[bot] merged 2 commits intocert-manager:masterfrom
jnoordsij:patch-1
Jan 25, 2026
Merged

Remove outdated information regarding Let's Encrypt ACME client behavior#1916
cert-manager-prow[bot] merged 2 commits intocert-manager:masterfrom
jnoordsij:patch-1

Conversation

@jnoordsij
Copy link
Contributor

Per https://letsencrypt.org/2025/06/26/expiration-notification-service-has-ended Let's Encrypt no longer stores the email address provided via the ACME API for any kind of account-related updates:

We have deleted the email addresses provided to Let’s Encrypt via the ACME API that were stored in our CA database in association with issuance data. This doesn’t affect addresses signed up to mailing lists and other systems. They are managed in a separate ISRG system unassociated with issuance data.
Going forward, if an email address is provided to Let’s Encrypt via the ACME API, Let’s Encrypt will not store the address but will instead forward it to the general ISRG mailing list system unassociated with any account data. If the email address has not been seen before, that system may send an onboarding email with information about how to subscribe to various sources of updates.

Note that it may also be worthwhile exploring dropping this field entirely in a variety of examples here and elsewhere, however this is left out for the purpose of this PR.

Signed-off-by: Jesper Noordsij <45041769+jnoordsij@users.noreply.github.com>
@cert-manager-prow cert-manager-prow bot added dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 14, 2026
@netlify
Copy link

netlify bot commented Jan 14, 2026

Deploy Preview for cert-manager ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 9c4e19e
🔍 Latest deploy log https://app.netlify.com/projects/cert-manager/deploys/6967a14f7d397b00088adbce
😎 Deploy Preview https://deploy-preview-1916--cert-manager.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Signed-off-by: Jesper Noordsij <45041769+jnoordsij@users.noreply.github.com>
Copy link
Member

@erikgb erikgb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jnoordsij! 🚀 Feel free to submit a follow-up PR to clean out usage of the email field in the Let's Encrypt examples.

/lgtm
/approve

@cert-manager-prow cert-manager-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jan 25, 2026
@cert-manager-prow
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: erikgb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cert-manager-prow cert-manager-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 25, 2026
@cert-manager-prow cert-manager-prow bot merged commit adda23c into cert-manager:master Jan 25, 2026
7 checks passed
@jnoordsij jnoordsij deleted the patch-1 branch January 26, 2026 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants