Reevaluate using SendGrid for sending release announcement emails

kubernetes / release

Release infrastructure for Kubernetes and related components

Apache License 2.0

485 stars 502 forks source link

Reevaluate using SendGrid for sending release announcement emails #3175

Open xmudrii opened 1 year ago

xmudrii commented 1 year ago

What would you like to be added:

Lately SendGrid hasn't been very reliable for sending release announcement emails using krel announce

We're often facing problems such as:

Emails not getting delivered to all mailing lists (lately they're getting delivered only to k-announce)
Folks having random issues with their SendGrid account
SendGrid deactivating account after some time of inactivity requiring a new account to be created

We should consider:

If we can fix those issues with SendGrid
If there are any other offerings that provide better user experience for our use case

Why is this needed:

It's important that the Release Managers can reliably send release announcement emails after cutting releases as many end users and Kubernetes developers depend on these emails.

xmudrii commented 1 year ago

Relevant discussion: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1690274036517309

ameukam commented 1 year ago

AWS Simple Email Service looks like a great alternative.

jimangel commented 1 year ago

I mentioned in Slack, but for record, I plan on seeing how challenging it would be to implement using a Google app password - which could be a good bridge to using a more robust approach (SES/group sending/etc). I'm reluctant to assign myself if others want to look at a more permanent approach - but keep me in the loop please!

saschagrunert commented 1 year ago

I'm in favor of switching to something more suitable :+1:

cpanato commented 1 year ago

i like the idea to use the aws email service! we also can use the patch notify that i was working and need to complete 😅

k8s-triage-robot commented 9 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

xmudrii commented 9 months ago

/remove-lifecycle stale

k8s-triage-robot commented 6 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

xmudrii commented 6 months ago

/lifecycle frozen