Mirrors/flux2
1
0
Fork 0
mirror of synced 2026-02-06 10:55:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update notification-controller to v0.0.1

Browse Source
This commit is contained in:
stefanprodan
2020-07-07 10:03:34 +03:00
parent 789fd34c4a
commit ad655183e0
7 changed files with 16 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/_files/notification-controller.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 43 KiB

15
docs/components/notification/controller.md
View File

@@ -1,14 +1,15 @@
# Notification Controller
The Notification Controller is a Kubernetes operator,
specialized in dispatching events to external systems such as
Slack, Microsoft Teams, Discord and Rocket chat.
The Notification Controller is a Kubernetes operator, specialized in handling inbound and outbound events.
The controller receives events via HTTP and dispatch them to external
webhooks based on event severity and involved objects.
![](../../_files/notification-controller.png)
The controller can be configured with Kubernetes custom resources that
define how events are processed and where to dispatch them.
The controller handles events coming from external systems (GitHub, GitLab, Bitbucket, Harbour, Jenkins, etc)
and notifies the GitOps toolkit controllers about source changes.
The controller handles events emitted by the GitOps toolkit controllers (source, kustomize, helm)
and dispatches them to external systems (Slack, Microsoft Teams, Discord, Rocker)
based on event severity and involved objects.
Links:

4
docs/guides/notifications.md
View File

@@ -42,9 +42,9 @@ spec:
name: slack-url
```
The provider type can be `slack`, `msteams`, `discord`, `rocket` or `webhook`.
The provider type can be `slack`, `msteams`, `discord`, `rocket` or `generic`.
When type `webhook` is specified, the notification controller will post the incoming
When type `generic` is specified, the notification controller will post the incoming
[event](../components/notification/event.md) in JSON format to the webhook address.
This way you can create custom handlers that can store the events in
Elasticsearch, CloudWatch, Stackdriver, etc.

3
docs/index.md
View File

@@ -29,7 +29,7 @@ Target features:
- External events handling (webhook receivers)
- Source write-back (automated patching)
- Policy driven validation (OPA, admission controllers)
- Seamless integration with Git providers (GitHub, GitLab, BitBucket)
- Seamless integration with Git providers (GitHub, GitLab, Bitbucket)
- Interoperability with workflow providers (GitHub Actions, Tekton, Argo)
- Interoperability with CAPI providers
@@ -44,6 +44,7 @@ Components:
- [Notification Controller](components/notification/controller.md)
- [Provider CRD](components/notification/provider.md)
- [Alert CRD](components/notification/alert.md)
- [Receiver CRD](components/notification/receiver.md)
- Helm Controller (TBA)
To get started with the toolkit please follow this [guide](get-started/index.md).