Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FLUX DOCS: don't use legacy slack config in example #1351

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions content/en/flux/guides/notifications.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,15 +27,17 @@ The notification controller is part of the default Flux installation.

## Define a provider

First create a secret with your Slack incoming webhook:
First create a secret with your Slack Bot token:

```sh
kubectl -n flux-system create secret generic slack-url \
--from-literal=address=https://hooks.slack.com/services/YOUR/SLACK/WEBHOOK
--from-literal=token=YOUR-SLACK-BOT-APP-TOKEN
```

Note that the secret must contain an `address` field,
it can be a Slack, Microsoft Teams, Discord or Rocket webhook URL.
{{% alert color="info" title="Alert Provider Configuration" %}}
Note that for token based providers (Slack, Telegram) the secret must contain a `token` field, for address based providers (Teams, Discord) the secret must contain an `address` field. See [Notification>Provider](https://fluxcd.io/flux/components/notification/provider/) section for more details.
{{% /alert %}}


Create a notification provider for Slack by referencing the above secret:

Expand Down