chore(deps): update docker.io/library/node docker tag to v22.11.0

This reverts commit 98fe8fe2a4.

.drone.yml

@@ -12,7 +12,7 @@ platform:
 
 steps:
 - name: clone repository
-  image: git.cryptic.systems/volker.raschek/git:1.3.1
+  image: git.cryptic.systems/volker.raschek/git:1.4.0
 
 - name: helm lint
   commands:
@@ -26,7 +26,7 @@ steps:
 - name: markdown lint
   commands:
   - markdownlint *.md
-  image: git.cryptic.systems/volker.raschek/markdownlint:0.41.0
+  image: git.cryptic.systems/volker.raschek/markdownlint:0.42.0
   resources:
     limits:
       cpu: 150
@@ -73,7 +73,7 @@ platform:
 
 steps:
 - name: clone repository
-  image: git.cryptic.systems/volker.raschek/git:1.3.1
+  image: git.cryptic.systems/volker.raschek/git:1.4.0
 
 - name: helm unittest
   commands:
@@ -125,14 +125,14 @@ platform:
 
 steps:
 - name: clone repository
-  image: git.cryptic.systems/volker.raschek/git:1.3.1
+  image: git.cryptic.systems/volker.raschek/git:1.4.0
 
 - name: generate README
   commands:
   - npm install
   - npm run readme:parameters
   - npm run readme:lint
-  image: docker.io/library/node:22.9.0-alpine
+  image: docker.io/library/node:22.11.0-alpine
   resources:
     limits:
       cpu: 150
@@ -141,7 +141,7 @@ steps:
 - name: detect diff
   commands:
   - git diff --exit-code --name-only README.md
-  image: git.cryptic.systems/volker.raschek/git:1.3.1
+  image: git.cryptic.systems/volker.raschek/git:1.4.0
 
 - name: email-notification
   environment:
@@ -183,7 +183,7 @@ platform:
 
 steps:
 - name: clone repository
-  image: git.cryptic.systems/volker.raschek/git:1.3.1
+  image: git.cryptic.systems/volker.raschek/git:1.4.0
 
 - name: release-helm-chart
   commands:

Chart.yaml

@@ -10,8 +10,9 @@ appVersion: "0.15.0"
 
 keywords:
 - prometheus
-- prometheus exporter
+- prometheus-exporter
-- postgres
+- postgres-postgres-exporter
+- postgres-exporter
 
 sources:
 - https://github.com/prometheus-community/postgres_exporter

README.md

@@ -66,9 +66,9 @@ The following examples serve as individual configurations and as inspiration for
 The first example shows how to deploy the metric exporter with TLS encryption. The verification of the custom TLS
 certification will be skipped by Prometheus.
 
-> [!WARN]
+> [!WARNING]
-> A TLS secret with the name `prometheus-postgresql-exporter-http` containing a `ca.crt`, `tls.key` and `tls.crt` is
+> The secret `prometheus-postgresql-exporter-http` containing the TLS certificate is already present. The keys `ca.crt`,
-> already present.
+> `tls.key` and `tls.crt` of the secret can be mounted into the container filesystem for TLS authentication / encryption.
 
 ```bash
 helm install prometheus-exporters/prometheus-postgres-exporter prometheus-postgres-exporter \

templates/prometheus-postgres-exporter/serviceAccount.yaml

@@ -13,7 +13,6 @@ metadata:
   {{- end }}
   name: {{ include "prometheus-postgres-exporter.fullname" . }}
   namespace: {{ .Release.Namespace }}
-spec:
 automountServiceAccountToken: {{ .Values.serviceAccount.new.automountServiceAccountToken }}
 {{- with .Values.serviceAccount.new.imagePullSecrets }}
 imagePullSecrets:

unittests/serviceAccounts/serviceAccount.yaml

@@ -29,12 +29,12 @@ tests:
   - notExists:
       path: metadata.labels
   - equal:
-      path: spec.automountServiceAccountToken
+      path: automountServiceAccountToken
       value: true
   - notExists:
-      path: spec.imagePullSecrets
+      path: imagePullSecrets
   - notExists:
-      path: spec.secrets
+      path: secrets
 
 
 - it: Rendering serviceAccount with custom values.
@@ -65,14 +65,14 @@ tests:
       path: metadata.name
       value: prometheus-postgres-exporter-unittest
   - equal:
-      path: spec.automountServiceAccountToken
+      path: automountServiceAccountToken
       value: false
   - equal:
-      path: spec.imagePullSecrets
+      path: imagePullSecrets
       value:
         - name: "my-pull-secret"
   - equal:
-      path: spec.secrets
+      path: secrets
       value:
       - name: "my-secret"
         namespace: "my-namespace"