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

.gitea/workflows/generate-readme.yaml

@@ -5,8 +5,6 @@ on:
     paths: [ "README.md", "values.yaml" ]
     types: [ "opened", "reopened", "synchronize" ]
   push:
-    branches:
-    - '**'
     paths: [ "README.md", "values.yaml" ]
     tags-ignore:
     - '**'

.gitea/workflows/helm.yaml

@@ -4,8 +4,6 @@ on:
   pull_request:
     types: [ "opened", "reopened", "synchronize" ]
   push:
-    branches:
-    - '**'
     tags-ignore:
     - '**'
   workflow_dispatch: {}
@@ -13,7 +11,7 @@ on:
 jobs:
   helm-lint:
     container:
-      image: docker.io/volkerraschek/helm:3.16.4
+      image: docker.io/volkerraschek/helm:3.16.1
     runs-on:
     - ubuntu-latest
     steps:
@@ -28,7 +26,7 @@ jobs:
 
   helm-unittest:
     container:
-      image: docker.io/volkerraschek/helm:3.16.4
+      image: docker.io/volkerraschek/helm:3.16.1
     runs-on:
     - ubuntu-latest
     steps:

.gitea/workflows/markdown-linters.yaml

@@ -5,8 +5,6 @@ on:
     paths: [ "**/*.md" ]
     types: [ "opened", "reopened", "synchronize" ]
   push:
-    branches:
-    - '**'
     paths: [ "**/*.md" ]
     tags-ignore:
     - '**'

.gitea/workflows/release.yaml

@@ -8,7 +8,7 @@ on:
 jobs:
   publish-chart:
     container:
-      image: docker.io/volkerraschek/helm:3.16.4
+      image: docker.io/volkerraschek/helm:3.16.1
     runs-on: ubuntu-latest
     steps:
       - name: Install tooling

README.md

@@ -46,7 +46,7 @@ version of the chart must be in sync with the `values.yaml`. Newer *minor* versi
 versions can break something!
 
 ```bash
-CHART_VERSION=0.3.1
+CHART_VERSION=0.1.0
 helm show values prometheus-exporters/prometheus-postgres-exporter --version "${CHART_VERSION}" > values.yaml
 ```
 
@@ -63,35 +63,6 @@ for customizations. These can be configured in more detail via `values.yaml`.
 
 The following examples serve as individual configurations and as inspiration for how deployment problems can be solved.
 
-#### Avoid CPU throttling by defining a CPU limit
-
-If the application is deployed with a CPU resource limit, Prometheus may throw a CPU throttling warning for the
-application. This has more or less to do with the fact that the application finds the number of CPUs of the host, but
-cannot use the available CPU time to perform computing operations.
-
-The application must be informed that despite several CPUs only a part (limit) of the available computing time is
-available. As this is a Golang application, this can be implemented using `GOMAXPROCS`. The following example is one way
-of defining `GOMAXPROCS` automatically based on the defined CPU limit like `100m`. Please keep in mind, that the CFS
-rate of `100ms` - default on each kubernetes node, is also very important to avoid CPU throttling.
-
-Further information about this topic can be found [here](https://kanishk.io/posts/cpu-throttling-in-containerized-go-apps/).
-
-> [!NOTE]
-> The environment variable `GOMAXPROCS` is set automatically, when a CPU limit is defined. An explicit configuration is
-> not anymore required.
-
-```bash
-helm install prometheus-postgres-exporter prometheus-exporters/prometheus-postgres-exporter \
-  --set 'config.database.secret.databaseUsername=postgres' \
-  --set 'config.database.secret.databasePassword=postgres' \
-  --set 'config.database.secret.databaseConnectionUrl="postgres.example.local:5432/postgres?ssl=disable"' \
-  --set 'prometheus.metrics.enabled=true' \
-  --set 'prometheus.metrics.serviceMonitor.enabled=true' \
-  --set 'deployment.postgresExporter.env.name=GOMAXPROCS' \
-  --set 'deployment.postgresExporter.env.valueFrom.resourceFieldRef.resource=limits.cpu' \
-  --set 'deployment.postgresExporter.resources.limits.cpu=100m'
-```
-
 #### TLS authentication and encryption
 
 The first example shows how to deploy the metric exporter with TLS encryption. The verification of the custom TLS
@@ -248,7 +219,7 @@ deployment:
 | `deployment.replicas`                              | Number of replicas for the postgres-exporter deployment.                                                   | `1`                                     |
 | `deployment.restartPolicy`                         | Restart policy of the postgres-exporter deployment.                                                        | `""`                                    |
 | `deployment.securityContext`                       | Security context of the postgres-exporter deployment.                                                      | `{}`                                    |
-| `deployment.strategy.type`                         | Strategy type - `Recreate` or `Rollingupdate`.                                                             | `Rollingupdate`                         |
+| `deployment.strategy.type`                         | Strategy type - `Recreate` or `Rollingupdate`.                                                             | `Recreate`                              |
 | `deployment.strategy.rollingUpdate.maxSurge`       | The maximum number of pods that can be scheduled above the desired number of pods during a rolling update. | `1`                                     |
 | `deployment.strategy.rollingUpdate.maxUnavailable` | The maximum number of pods that can be unavailable during a rolling update.                                | `1`                                     |
 | `deployment.terminationGracePeriodSeconds`         | How long to wait until forcefully kill the pod.                                                            | `60`                                    |

renovate.json

@@ -3,6 +3,7 @@
   "assignees": [ "volker.raschek" ],
   "customManagers": [
     {
+      "description": "Update container image reference",
       "fileMatch": [
         "^Chart\\.yaml$"
       ],
@@ -15,18 +16,25 @@
       "versioningTemplate": "semver"
     },
     {
+      "description": "Detect helm chart version in README",
       "fileMatch": ["^README\\.md$"],
       "matchStrings": [
-        "VERSION=(?<currentValue>.*)"
+        "^CHART_VERSION=(?<currentValue>.*)$"
       ],
+      "datasourceTemplate": "git-tags",
       "depNameTemplate": "volker.raschek/prometheus-postgres-exporter",
       "packageNameTemplate": "https://git.cryptic.systems/volker.raschek/prometheus-postgres-exporter",
-      "datasourceTemplate": "git-tags",
       "versioningTemplate": "semver"
     }
   ],
   "labels": [ "renovate" ],
   "packageRules": [
+    {
+      "addLabels": [ "renovate/automerge", "renovate/droneci" ],
+      "automerge": true,
+      "matchManagers": "droneci",
+      "matchUpdateTypes": [ "minor", "patch"]
+    },
     {
       "addLabels": [ "renovate/automerge", "renovate/npm" ],
       "automerge": true,
@@ -34,20 +42,6 @@
       "matchManagers": [ "npm" ],
       "matchUpdateTypes": [ "minor", "patch"]
     },
-    {
-      "addLabels": [ "renovate/automerge", "renovate/container" ],
-      "automerge": true,
-      "excludePackagePatterns": [
-        "prometheuscommunity/postgres-exporter"
-      ],
-      "matchDatasources": [
-        "docker"
-      ],
-      "matchUpdateTypes": [
-        "minor",
-        "patch"
-      ]
-    },
     {
       "addLabels": [ "renovate/automerge", "renovate/documentation" ],
       "automerge": true,

templates/prometheus-postgres-exporter/_deployment.tpl

@@ -9,17 +9,6 @@
 {{- end }}
 {{- end }}
 
-{{/* env */}}
-
-{{- define "prometheus-postgres-exporter.deployment.env" -}}
-{{- $env := dict "env" (.Values.deployment.postgresExporter.env | default (list) ) }}
-{{- if and (hasKey .Values.deployment.postgresExporter.resources "limits") (hasKey .Values.deployment.postgresExporter.resources.limits "cpu") }}
-{{- $env = merge $env (dict "env" (list (dict "name" "GOMAXPROCS" "valueFrom" (dict "resourceFieldRef" (dict "divisor" "1" "resource" "limits.cpu"))))) }}
-{{- end }}
-{{ toYaml $env }}
-{{- end -}}
-
-
 {{/* envFrom */}}
 
 {{- define "prometheus-postgres-exporter.deployment.envFrom" -}}

templates/prometheus-postgres-exporter/deployment.yaml

@@ -34,10 +34,9 @@ spec:
         {{- range .Values.deployment.postgresExporter.args }}
         - {{ . | quote }}
         {{- end }}
-        {{- $env := (include "prometheus-postgres-exporter.deployment.env" . | fromYaml) }}
+        {{- with .Values.deployment.postgresExporter.env }}
-        {{- if and (hasKey $env "env") (gt (len $env.env) 0) }}
         env:
-        {{- toYaml $env.env | nindent 8 }}
+        {{- toYaml . | nindent 8 }}
         {{- end }}
         {{- $envFrom := (include "prometheus-postgres-exporter.deployment.envFrom" . | fromYaml) }}
         {{- if hasKey $envFrom "envFrom" }}
@@ -126,7 +125,3 @@ spec:
       volumes:
       {{- toYaml $volumes.volumes | nindent 6 }}
       {{- end }}
-  {{- with .Values.deployment.strategy }}
-  strategy:
-    {{- toYaml . | nindent 4 }}
-  {{- end }}

unittests/deployment/deployment.yaml

@@ -95,13 +95,6 @@ tests:
       path: spec.template.spec.tolerations
   - notExists:
       path: spec.template.spec.topologySpreadConstraints
-  - equal:
-      path: spec.strategy
-      value:
-        type: "Rollingupdate"
-        rollingUpdate:
-          maxSurge: 1
-          maxUnavailable: 1
 
 - it: Test custom replicas
   set:
@@ -234,14 +227,6 @@ tests:
         cpu: 25m
         memory: 100MB
   asserts:
-  - equal:
-      path: spec.template.spec.containers[0].env
-      value:
-      - name: GOMAXPROCS
-        valueFrom:
-          resourceFieldRef:
-            divisor: "1"
-            resource: limits.cpu
   - equal:
       path: spec.template.spec.containers[0].resources
       value:

values.yaml

@@ -228,7 +228,7 @@ deployment:
   ## @param deployment.strategy.rollingUpdate.maxSurge The maximum number of pods that can be scheduled above the desired number of pods during a rolling update.
   ## @param deployment.strategy.rollingUpdate.maxUnavailable The maximum number of pods that can be unavailable during a rolling update.
   strategy:
-    type: "Rollingupdate"
+    type: "Recreate"
     rollingUpdate:
       maxSurge: 1
       maxUnavailable: 1
@@ -266,7 +266,7 @@ grafana:
   enabled: false
 
   ## @param grafana.dashboardDiscoveryLabels Labels that Grafana uses to discover resources. The labels may vary depending on the Grafana deployment.
-  ## @skip grafana.dashboardDiscoveryLabels Skip individual configuration.
+  ## @skip grafana.dashboardDiscoveryLabels
   dashboardDiscoveryLabels:
     grafana_dashboard: "1"