- Features
- [Introduce Slack notifications support for workflow running on Argo Workflows](features.1)
Features
<a id='features.1'></a>Introduce Slack notifications support for workflow running on Argo Workflows
With this release, Metaflow users can get notified on Slack when their workflows succeed or fail on Argo Workflows. Using this feature is quite straightforward
1. Follow [these instructions](https://api.slack.com/messaging/webhooks) on Slack to set up incoming webhooks for your Slack workspace.
2. You should now have a webhook URL that Slack provides. Here is an example webhook:
https://hooks.slack.com/services/T0XXXXXXXXX/B0XXXXXXXXX/qZXXXXXX
3. To enable notifications on Slack when your Metaflow flow running on Argo Workflows succeeds or fails, deploy it using the _--notify-on-error_ or _--notify-on-success_ flags:
python flow.py argo-workflows create --notify-on-error --notify-on-success --notify-slack-webhook-url <slack-webhook-url>
4. You can also set `METAFLOW_ARGO_WORKFLOWS_CREATE_NOTIFY_SLACK_WEBHOOK_URL=<slack-webhook-url>` in your environment instead of specifying _--notify-slack-webhook-url_ on the CLI everytime.
5. Next time your workflow succeeds or fails on Argo Workflows, you will get a helpful notification on Slack.
FAQ
_I deployed my workflow following the instructions above, but I haven’t received any notifications yet?_
This issue may very well happen if you are running Kubernetes v1.24 or newer.
Since v1.24, Kubernetes stopped automatically creating a secret for every serviceAccount. Argo Workflows relies on the existence of these secrets to run lifecycle hooks responsible for the emission of these notifications.
Follow these steps for explicitly creating a secret for the service account that responsible for executing Argo Workflows steps:
1. Run the following command, replacing _service-account.name_ with the _serviceAccount_ in your deployment. Also change the name of the secret to correctly reflect the name of the _serviceAccount _for which this secret is
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Secret
metadata:
name: default-sa-token change according to the name of the sa
annotations:
kubernetes.io/service-account.name: default replace with your sa
type: kubernetes.io/service-account-token
EOF
3. Edit the _serviceAccount_ object so as to add the name of the above secret in it. You can use _kubectl edit_ for this. The _serviceAccount_ yaml should look like the following
$ kubectl edit sa default -n mynamespace
...
apiVersion: v1
kind: ServiceAccount
metadata:
creationTimestamp: "2023-05-05T20:58:58Z"
name: default
namespace: jobs-default
resourceVersion: "6739507"
uid: 4a708eff-d6ba-4dd8-80ee-8fb3c4c1e1c7
secrets:
- name: default-sa-token should match the secret above
4. That’s it! Try executing your workflow again on Argo Workflows. If you are still running into issues, reach out to us!
In case you need any assistance or have feedback for us, ping us at [chat.metaflow.org](http://chat.metaflow.org) or open a GitHub issue.
---
What's Changed
* feature: add argo events environment variables to `metaflow configure kubernetes` by saikonen in https://github.com/Netflix/metaflow/pull/1405
* handle whitespaces in argo events parameters by savingoyal in https://github.com/Netflix/metaflow/pull/1408
* Add back comment for argo workflows by savingoyal in https://github.com/Netflix/metaflow/pull/1409
* Support ArgoEvent object with kubernetes by savingoyal in https://github.com/Netflix/metaflow/pull/1410
* Print workflow template location as part of argo-workflows create by savingoyal in https://github.com/Netflix/metaflow/pull/1411
**Full Changelog**: https://github.com/Netflix/metaflow/compare/2.8.6...2.9.0