2018-03-22 04:19:55 +08:00
|
|
|
Make sure to define the following settings in `values.yaml`:
|
|
|
|
|
|
|
|
|
|
env:
|
|
|
|
|
- CLOUDWATCH_NAMESPACE
|
|
|
|
|
- CLOUDWATCH_REGION
|
|
|
|
|
- CLOUDWATCH_PUBLISH_TIMEOUT
|
|
|
|
|
- PROMETHEUS_SCRAPE_INTERVAL
|
|
|
|
|
- PROMETHEUS_SCRAPE_URL
|
2018-03-22 04:37:50 +08:00
|
|
|
- CERT_PATH
|
|
|
|
|
- KEY_PATH
|
|
|
|
|
- ACCEPT_INVALID_CERT
|
2019-06-21 23:50:30 +08:00
|
|
|
# Optionally:
|
|
|
|
|
- INCLUDE_METRICS
|
|
|
|
|
- EXCLUDE_METRICS
|
2019-10-15 02:24:14 +08:00
|
|
|
- INCLUDE_DIMENSIONS_FOR_METRICS
|
|
|
|
|
- EXCLUDE_DIMENSIONS_FOR_METRICS
|
2018-03-22 04:19:55 +08:00
|
|
|
|
|
|
|
|
secrets:
|
|
|
|
|
- AWS_ACCESS_KEY_ID
|
|
|
|
|
- AWS_SECRET_ACCESS_KEY
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you deploying the module in AWS on Kubernetes with `kube2iam` to assume an IAM Role with permissions
|
|
|
|
|
to publish metrics to CloudWatch, don't provide the AWS credentials in 'secrets'.
|
|
|
|
|
The chain of credential providers will search for credentials in EC2 Instance Roles.
|
