forked from jeefy/kippy
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
33 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,36 @@ | ||
# Kippy | ||
|
||
Your Kubernetes Insurance Policy (KIP-Y). But y'know. Mainly for homelabs. | ||
Your Kubernetes Insurance Policy (KIP-Y). But probably not for enterprises. | ||
|
||
## Quickstart | ||
|
||
``` | ||
kubectl apply -f https://raw.githubusercontent.com/jeefy/kippy/refs/heads/main/deployment.yaml | ||
``` | ||
|
||
Then edit the secret and cycle the pod. :) | ||
|
||
## What does it do? | ||
|
||
KIPPY is meant to be simple. It watches all events emitted by the Kubernetes API Server. | ||
|
||
Any not-normal event emitted is then collected and sent to configured notification sinks every 60s. | ||
|
||
### Notification Sinks | ||
|
||
- Discord | ||
- Slack | ||
- Sendgrid | ||
- Generic Webhook | ||
|
||
## Prior art | ||
|
||
https://github.com/redhat-cop/k8s-notify | ||
|
||
https://github.com/opsgenie/kubernetes-event-exporter | ||
|
||
## Why? | ||
|
||
1. A lot of the previous examples are archived. | ||
2. I like reinventing the wheel. | ||
3. This matches my exact use-case. |