add email & slack notifier action in github workflow

[mohitsethia]

What this PR does / why we need it:
Adds email and slack notification workflow action template for weekly security scan.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2179

Special notes for your reviewer:

/area provider/ibmcloud

1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

[linux-foundation-easycla]

• ✅login: mohitsethia / (1f4a0ee)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mohitsethia
Once this PR has been reviewed and has the lgtm label, please assign mkumatag for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Hi @mohitsethia. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-ibmcloud ready!

Name	Link
🔨 Latest commit	1f4a0ee
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-ibmcloud/deploys/67e989557be06d0008600a96
😎 Deploy Preview	https://deploy-preview-2280.cluster-api-ibmcloud.sigs.k8s.io
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[Prajyot-Parab]

@anshuman-agarwala can you help validating these changes.

[mkumatag]

But the basic Q - where do you want to report these? which slack channel? and what email id and which smtp server it uses to send the mails?

[anshuman-agarwala]

We can't use k8s slack since they don't give out webhook links for their channels. For the email, I think on a job failure Github sends out an email already, not sure how useful sending an email notification will be.

[mkumatag]

We can't use k8s slack since they don't give out webhook links for their channels. For the email, I think on a job failure Github sends out an email already, not sure how useful sending an email notification will be.

Hmm, in that case, maybe it's not worth spending our time on this.

[mohitsethia]

Is it the limitation of the slack feature for kubernetes only? Because my employers slack version provides creating webhook, maybe the admin of the k8s slack can help create one?

And I was not sure what notification was being talked about in the issue and I didn't get any response so I went ahead giving an example of both the both slack and email action workflows. I guess github only emails to the person who raised the PR and not the maintainers/contributor/whoever wants to receive the notification, but not sure how that works for k8s workgroup.

[anshuman-agarwala]

Is it the limitation of the slack feature for kubernetes only? Because my employers slack version provides creating webhook, maybe the admin of the k8s slack can help create one?

And I was not sure what notification was being talked about in the issue and I didn't get any response so I went ahead giving an example of both the both slack and email action workflows. I guess github only emails to the person who raised the PR and not the maintainers/contributor/whoever wants to receive the notification, but not sure how that works for k8s workgroup.

It's a limitation placed on us by the kubernetes slack admins: https://github.com/kubernetes/community/blob/master/communication/slack-guidelines.md#requesting-a-bot-token-or-webhook