As part of applying this helm chart the configMap statping is created. This configMap may contain:
apiVersion: v1
data:
DB_CONN: postgres
DB_DATABASE: statping
DB_HOST: CENSORED
DB_PASS: CENSORED
DB_PORT: "5432"
DB_USER: statping
DEBUG: "1"
DISABLE_COLORS: "true"
PORT: "8080"
POSTGRES_SSLMODE: require
READ_ONLY: "false"
kind: ConfigMap
metadata:
annotations:
meta.helm.sh/release-name: statping
meta.helm.sh/release-namespace: alm
creationTimestamp: "2024-01-19T04:10:45Z"
labels:
app.kubernetes.io/managed-by: Helm
name: statping
namespace: alm
resourceVersion: "202811663"
uid: 591735bc-3fa7-47f0-95f6-72462c848995
(fetched using kubectl get cm -n alm statping -o yaml
I have censored the hostname and password in the output.
Passwords and other sensitive information should be stored in secrets, as there may be people running around the cluster with privileges to read ConfigMaps (for easy maintenance, changing configs) but they can't read secrets (to keep the secrets actually secret!)
I can provide a PR if this is a desirable change.
As part of applying this helm chart the configMap
statpingis created. This configMap may contain:(fetched using
kubectl get cm -n alm statping -o yamlI have censored the hostname and password in the output.
Passwords and other sensitive information should be stored in secrets, as there may be people running around the cluster with privileges to read ConfigMaps (for easy maintenance, changing configs) but they can't read secrets (to keep the secrets actually secret!)
I can provide a PR if this is a desirable change.