Reevaluate using SendGrid for sending release announcement emails

[xmudrii]

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]

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

[ameukam]

AWS Simple Email Service looks like a great alternative.

[jimangel]

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]

I'm in favor of switching to something more suitable 👍

[cpanato]

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]

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]

/remove-lifecycle stale

[k8s-triage-robot]

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]

/lifecycle frozen