You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Typically we have sites that are owned by teams, and those teams have their own flowdock (or slack) channels.
We already have notifications (alertmanager) sent (routed) to specific teams based on labels on the Deployment, for example:
labels:
app.kubernetes.io/owner: cluster-ops
These should probably be annotations instead ;)
It would be nice to have kube-lookout be able to notify different slack channels based on such annotations.
It's probably risky to have slack tokens inside the deployment as an annotation, so it could be that kube-lookout keeps a configuration (a map) of owners to slack channel tokens (or flowdock etc).
The text was updated successfully, but these errors were encountered:
Typically we have sites that are owned by teams, and those teams have their own flowdock (or slack) channels.
We already have notifications (alertmanager) sent (routed) to specific teams based on labels on the Deployment, for example:
These should probably be annotations instead ;)
It would be nice to have
kube-lookout
be able to notify different slack channels based on such annotations.It's probably risky to have slack tokens inside the deployment as an annotation, so it could be that
kube-lookout
keeps a configuration (a map) of owners to slack channel tokens (or flowdock etc).The text was updated successfully, but these errors were encountered: