Add testing workflow for Helm chart

.github/workflows/lint-test.yaml

@@ -0,0 +1,49 @@
+name: Lint and Test Charts
+
+on:
+  # Run CI against all pushes (direct commits, also merged PRs), Pull Requests
+  push:
+    branches: [main]
+    paths:
+      - 'charts/**'
+      - '.github/workflows/lint-test.yml'
+  pull_request:
+    # The branches below must be a subset of the branches above
+    branches: [main]
+    paths:
+      - 'charts/**'
+      - '.github/workflows/lint-test.yml'
+
+jobs:
+  lint-test:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+
+      - name: Set up Helm
+        uses: azure/setup-helm@v4.2.0
+        with:
+          version: v3.17.0
+
+      - uses: actions/setup-python@v5.3.0
+        with:
+          python-version: '3.x'
+          check-latest: true
+
+      - name: Set up chart-testing
+        uses: helm/chart-testing-action@v2.7.0
+
+      - name: Update values.yaml
+        run: cp charts/kavir/values.yaml.template charts/kavir/values.yaml
+
+      - name: Run chart-testing (lint)
+        run: ct lint --target-branch ${{ github.event.repository.default_branch }}
+
+      - name: Create kind cluster
+        uses: helm/kind-action@v1.12.0
+
+      - name: Run chart-testing (install)
+        run: ct install --target-branch ${{ github.event.repository.default_branch }}

README.md

@@ -12,7 +12,7 @@ The container is based on [bitnamis kubectl container](https://github.com/bitnam
 
 ## helm chart
 
-The helm chart uses the container image described above to create a [kubernetes cronjob](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/) inside the kubernetes cluster which periodically updates the csv files in the predefined git repository. Look inside the `helm` folder to read more about it and how to use it.
+The helm chart uses the container image described above to create a [kubernetes cronjob](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/) inside the kubernetes cluster which periodically updates the csv files in the predefined git repository. Look inside the `charts/kavir/` folder to read more about it and how to use it.
 
 ## html-report-builder
 

helm/Chart.yaml → charts/kavir/Chart.yaml

@@ -5,5 +5,8 @@ version: 2.0.1
 description: kavir forwards information about applications in a kubernetes cluster to a git repository. This way software and stakeholders without access to the kubernetes cluster can still see the image names and versions that are used by the applications in the cluster.
 type: application
 home: https://github.com/telekom-mms/kavir
+maintainers:
+  - email: 128165622+I-Am-hehu@users.noreply.github.com
+    name: I-Am-hehu
 appVersion: "1.1.0"
 ...

helm/README.md → charts/kavir/README.md

@@ -38,4 +38,4 @@ The helm chart uses the container image described in the `docker` folder to crea
     * scopes: write_repository
 * create `values.yaml` from `values.yaml.template`
   * configure `values.yaml`
-* run `helm install kavir ./helm --namespace kavir --create-namespace`
+* run `helm install kavir ./charts/kavir --namespace kavir --create-namespace`

helm/values.yaml.template → charts/kavir/values.yaml.template

@@ -22,4 +22,3 @@ report:
     jobs: false
     cronjobs: false
     replicationcontrollers: false
-...

docker/README.md

@@ -4,7 +4,7 @@ The container is based on [bitnamis kubectl container](https://github.com/bitnam
 
 ## environment variables
 
-The container requires several environment variables. Since kavir is meant to be run inside a kubernetes cluster it is recommended to use the helm chart to deploy kavir. The `values.yaml` of the helm chart contains all environment variables. Look inside the `helm` folder for further explanations.
+The container requires several environment variables. Since kavir is meant to be run inside a kubernetes cluster it is recommended to use the helm chart to deploy kavir. The `values.yaml` of the helm chart contains all environment variables. Look inside the `charts/kavir/` folder for further explanations.
 
 | variable                     | description                                                                                   |
 | ---------------------------- | --------------------------------------------------------------------------------------------- |