statping / charts Goto Github PK

When trying to use the helm chart to install, it doesn't startup in setup mode, nor does admin/admin work. What is the ideal workflow? Can we document it?

I also tried using sqlite3 to update the password as #798 describes, but the database is locked by statping, and killing it causes the pod to restart, and relock it.

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.

The chart default values are: https://github.com/statping/charts/blob/main/charts/statping/values.yaml

ingress:
  # ingress.enabled -- Enable ingress
  enabled: false
  pathType: Prefix
  tls: false
  annotations: {}
  hostname: grafana.local
  secretName: statping-cert
  path: /
  secrets: []

Implying that by default no ingress would be created.

The chart implementation code creates one anyway tough: https://github.com/statping/charts/blob/main/charts/statping/templates/ingress.yaml

The enabled flag from the values.yaml is not queried in the code at all.

Can provide PR if OK.