github/deprecated-helm-charts
1
0
Fork 0
mirror of https://github.com/helm/charts.git synced 2026-08-23 22:37:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

[stable/prometheus-cloudwatch-exporter] additional docu on service account usage (#23028)

Browse Source 
* additional info on service account config so one can read mounted secret

this worked OK:
```
securityContext:
  runAsUser: 65534  # run as nobody user instead of root
  fsGroup: 65534 # to read mounted secret with the same id
```

Signed-off-by: Peter Triesz <peter.triesz@klar.mx>

* updating chart version after readme modification

Signed-off-by: Peter Triesz <peter.triesz@klar.mx>
This commit is contained in:
Peter Triesz
2020-07-01 13:52:00 -07:00
committed by GitHub
parent 35d4b2f944
commit af611b1e9a
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stable/prometheus-cloudwatch-exporter/Chart.yaml
+1 -1
View File
@@ -2,7 +2,7 @@ apiVersion: v1
appVersion: "0.8.0"
description: A Helm chart for prometheus cloudwatch-exporter
name: prometheus-cloudwatch-exporter
version: 0.8.1
version: 0.8.2
home: https://github.com/prometheus/cloudwatch_exporter
sources:
- https://github.com/prometheus/cloudwatch_exporter
stable/prometheus-cloudwatch-exporter/README.md
+1 -1
View File
@@ -15,7 +15,7 @@ This chart bootstraps a [cloudwatch exporter](http://github.com/prometheus/cloud
## Prerequisites
- [kube2iam](../../stable/kube2iam) installed to used the **aws.role** config option otherwise configure **aws.aws_access_key_id** and **aws.aws_secret_access_key** or **aws.secret.name**
- Or an [IAM Role for service account](https://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/) attached to a service account with an annotation. However, you cannot run the pod as nobody in `securityContext.runAsUser` as it won't be able to access the mounted secret.
- Or an [IAM Role for service account](https://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/) attached to a service account with an annotation. If you run the pod as nobody in `securityContext.runAsUser` then also set `securityContext.fsGroup` to the same value so it will be able to access to the mounted secret.
## Installing the Chart