Should release-notify script send from GCB?

[justaugustus]

(Follow-up item from kubernetes/sig-release#696)
ref: kubernetes/sig-release#666 (comment)

cc: @hoegaarden @tpepper @kubernetes/patch-release-team

/help
/sig release
/area release-eng
/milestone v1.18
/priority important-longterm
/kind feature

[hoegaarden]

Should release-notify script send from GCB?

Yes, I think it should.

Directly sending does not work, however sending mails via sendgrid works (other services will most probably work too, but that's what I have been using eg. in #949).

From what I can see, things we'd need to make this a reality:

• a sendgrid account
• a sendgrid secret in GCB (similar to the already existing one for the GitHub token)
• changes to the notify script to run on GCB and not locally

[justaugustus]

@hoegaarden -- Since you've already been working on this, I'm assigning you. Let's see if we have time in the releng meeting today to discuss.

/assign @hoegaarden
/remove-help

[hoegaarden]

To add some context here:
Sending mails is not directly possible from a GCP instance because the default smtp port is blocked. There are some workarounds and alternatives. Using a service like sendgrid seems to be the easiest.

See also:

• https://cloud.google.com/compute/docs/tutorials/sending-mail/
• https://cloud.google.com/cloud-build/docs/configure-third-party-notifications

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[xmudrii]

@hoegaarden @justaugustus I see that this issue is rotten and in the v1.18 milestone. Should we do anything about that?

[xmudrii]

/milestone v1.19
/remove-lifecycle rotten

[justaugustus]

I signed up for a Sendgrid account for this a while back, but it hasn't been high-priority.
Will try to close the loop on this this cycle.

/assign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[saschagrunert]

/remove-lifecycle stale

[saschagrunert]

@justaugustus is this still relevant to us? Manually announcing the release seems a legit step to me.

[saschagrunert]

Closing because I guess the process we're using right now is a great fit. I do not see a necessity to announce directly from krel.
/close

[k8s-ci-robot]

@saschagrunert: Closing this issue.

In response to this:

Closing because I guess the process we're using right now is a great fit. I do not see a necessity to announce directly from krel.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.