.gitea/workflows/helm.yaml

@@ -13,7 +13,7 @@ on:
 jobs:
   helm-lint:
     container:
-      image: docker.io/volkerraschek/helm:3.17.1
+      image: docker.io/volkerraschek/helm:3.16.4
     runs-on:
     - ubuntu-latest
     steps:
@@ -28,7 +28,7 @@ jobs:
 
   helm-unittest:
     container:
-      image: docker.io/volkerraschek/helm:3.17.1
+      image: docker.io/volkerraschek/helm:3.16.4
     runs-on:
     - ubuntu-latest
     steps:

.gitea/workflows/release.yaml

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

Chart.yaml

@@ -4,7 +4,7 @@ description: Prometheus metric exporter for PostgreSQL
 type: application
 kubeVersion: ">=1.20.0"
 version: "0.1.0"
-appVersion: "0.17.0"
+appVersion: "0.16.0"
 
 # icon: https://annotations.example.com/icon.png
 

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.4.0
+CHART_VERSION=0.3.2
 helm show values prometheus-exporters/prometheus-postgres-exporter --version "${CHART_VERSION}" > values.yaml
 ```
 
@@ -71,7 +71,7 @@ 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 `1000m`. Please keep in mind, that the CFS
+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/).
@@ -79,8 +79,6 @@ Further information about this topic can be found [here](https://kanishk.io/post
 > [!NOTE]
 > The environment variable `GOMAXPROCS` is set automatically, when a CPU limit is defined. An explicit configuration is
 > not anymore required.
->
-> Please take care the a CPU limit < `1000m` can also lead to CPU throttling. Please read the linked documentation carefully.
 
 ```bash
 helm install prometheus-postgres-exporter prometheus-exporters/prometheus-postgres-exporter \
@@ -91,7 +89,7 @@ helm install prometheus-postgres-exporter prometheus-exporters/prometheus-postgr
   --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=1000m'
+  --set 'deployment.postgresExporter.resources.limits.cpu=100m'
 ```
 
 #### TLS authentication and encryption

renovate.json

@@ -31,11 +31,6 @@
     "renovate"
   ],
   "lockFileMaintenance": {
-    "addLabels": [
-      "renovate/automerge",
-      "renovate/lockFileMaintenance"
-    ],
-    "automerge": true,
     "enabled": true
   },
   "npm": {

unittests/deployment/deployment.yaml

@@ -98,7 +98,7 @@ tests:
   - equal:
       path: spec.strategy
       value:
-        type: "RollingUpdate"
+        type: "Rollingupdate"
         rollingUpdate:
           maxSurge: 1
           maxUnavailable: 1