BotKube can be integrated with external apps via Webhooks. A webhook is essentially a POST request sent to a callback URL. So you can configure BotKube to send events on specified URL.
We will be using helm to install BotKube in Kubernetes. Follow this guide to install helm if you don’t have it installed already.
Add botkube chart repository:
$ helm repo add botkube https://charts.botkube.io
$ helm repo update
Deploy BotKube backend using helm install in your cluster:
$ helm install --version v0.12.4 botkube --namespace botkube --create-namespace \
--set communications.webhook.enabled=true \
--set communications.webhook.url=<WEBHOOK_URL> \
--set config.settings.clustername=<CLUSTER_NAME> \
--set image.tag=v0.12.4 \
botkube/botkube
where,
Configuration syntax is explained here. Full Helm chart parameters list is documented here.
With the default configuration, BotKube will watch all the resources in all the namespaces for create, delete and error events. If you wish to monitor only specific resources, follow the steps given below:
Create a new config.yaml
file and add Kubernetes resource configuration as described on the source page.
Pass the YAML file as a flag to helm install
command, e.g.:
helm install --version v0.12.4 --name botkube --namespace botkube --create-namespace -f /path/to/config.yaml --set=...other args..
Alternatively, you can also update the configuration at runtime as documented here
If you have installed BotKube backend using helm, execute following command to completely remove BotKube and related resources from your cluster
$ helm uninstall botkube