Repository navigation
Conversation
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Member
Author
|
/assign @saschagrunert @xmudrii @puerco @Verolop |
…eminders Signed-off-by: Carlos Panato <ctadeu@gmail.com>
cpanato
force-pushed
the
patch-notification-v2
branch
from
October 21, 2026 13:42
cdbeeca to
ee5585e
Compare
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.
What type of PR is this?
/kind feature
What this PR does / why we need it:
Revives #3627, rebased on master with the review feedback addressed.
Adds
cmd/patch-release-notification, an AWS Lambda that runs once a day, reads the patch release schedule, and emails the community through SES when a cherry-pick deadline isDAYS_TO_ALERTdays away. It runs in mock mode by default, which sends only to the sender address.Changes since #3627:
The schedule-builder model types move to
cmd/schedule-builder/modelso they can be shared.Infra: kubernetes/k8s.io#10093 (replaces kubernetes/k8s.io#6853).
Merge order: this PR first, then kubernetes/k8s.io#10093. Nothing is deployed on merge. After both merge: apply the CloudFormation bootstrap, push the image built from master with
ko, setimage_urito its digest in k8s.io, and runterraform apply. It starts in mock mode;no_mock = truecomes in a later k8s.io PR, after SES production access is granted.Which issue(s) this PR fixes:
Fixes #2174
Does this PR introduce a user-facing change?