@@ -9,18 +9,18 @@ Currently support alerting to Datadog and logs (ie. syslog).
9
9
Assuming you have go 1.9 and glide in the path, and GOPATH configured:
10
10
11
11
``` shell
12
- make dep
12
+ make deps
13
13
make build
14
14
```
15
15
16
16
## Usage
17
17
18
- The daemon may run as a pod in the cluster , or outside of the cluster.
19
- He should find the Kubernetes api-server automatically, but you can
20
- provide this server's address with "-s" flag, or a full config with "-k".
18
+ The daemon may run either as a pod, or outside of the Kubernetes cluster.
19
+ He should find the Kubernetes api-server automatically ( but you can
20
+ provide this server's address with "-s" flag, or a kube config with "-k") .
21
21
22
22
You can pass configuration values either by command line arguments, or
23
- environment variables, or with a yaml configuration file.
23
+ environment variables, a yaml configuration file, or a combination or those .
24
24
25
25
The command line flags are:
26
26
```
33
33
-i, --datadog-api-key string datadog api key
34
34
-a, --datadog-app-key string datadog app key
35
35
-d, --dry-run dry-run mode
36
- -p, --healthcheck-port int port for answering healtchecks
36
+ -p, --healthcheck-port int port for answering healthchecks
37
37
-h, --help help for kube-alert
38
38
-k, --kube-config string kube config path
39
39
-v, --log-level string log level (default "debug")
@@ -56,3 +56,16 @@ datadog:
56
56
app-key : xxx
57
57
` ` `
58
58
59
+ The environment variable consumed by kube-alert are option names prefixed
60
+ by ` ` ` KUBE_ALERT_``` and using underscore instead of dash. Except KUBECONFIG,
61
+ used without a prefix (to match kubernetes conventions).
62
+ ```
63
+ env KUBECONFIG=/etc/kube/config \
64
+ KUBE_ALERT_HEALTHCHECK_PORT=8081 \
65
+ KUBE_ALERT_DATADOG.APP_KEY="xxx" \
66
+ KUBE_ALERT_DATADOG.API_KEY="xxx" \
67
+ KUBE_ALERT_DRY_RUN=true \
68
+ KUBE_ALERT_LOG.LEVEL=info \
69
+ KUBE_ALERT_API_SERVER="http://example.com:8080 " \
70
+ kube-alert
71
+ ```
0 commit comments