From 9aa8f786206480c5a8c35e12a38bd69347fa1678 Mon Sep 17 00:00:00 2001
From: WS <59507751+Evantage-WS@users.noreply.github.com>
Date: Sun, 8 Dec 2024 17:24:43 +0100
Subject: [PATCH] charts update

---
 charts/dvwa/Chart.yaml          | 13 ++++++++++---
 charts/game-2048/Chart.yaml     | 24 +++++++++++++++++++++---
 charts/hello-rancher/Chart.yaml | 24 +++++++++++++++++++++---
 charts/nettools/Chart.yaml      | 26 ++++++++++++++++++++++----
 4 files changed, 74 insertions(+), 13 deletions(-)

diff --git a/charts/dvwa/Chart.yaml b/charts/dvwa/Chart.yaml
index 5910f46..930f165 100644
--- a/charts/dvwa/Chart.yaml
+++ b/charts/dvwa/Chart.yaml
@@ -1,6 +1,13 @@
+# See https://github.com/digininja/DVWA
 apiVersion: v2
-name: dvwa
-description: A Helm chart for DVWA
+name: evantage-dvwa
+description: Damn Vulnerable Web Application (DVWA), its main goal is to be an aid for security professionals to test their skills and tools
+maintainers:
+  - name: evantage
+    email: helm@evantage.nl
+annotations:
+  catalog.cattle.io/display-name: Evantage Nettools
+  catalog.cattle.io/release-name: evantage-nettools
 
 # A chart can be either an 'application' or a 'library' chart.
 #
@@ -21,7 +28,7 @@ version: 0.1.0
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "9ca729d"
+appVersion: 0.1.0
 
 dependencies:
   - name: mysql
diff --git a/charts/game-2048/Chart.yaml b/charts/game-2048/Chart.yaml
index ad41d7e..e5474ce 100644
--- a/charts/game-2048/Chart.yaml
+++ b/charts/game-2048/Chart.yaml
@@ -1,12 +1,30 @@
 apiVersion: v2
 name: game-2048
 description: Game 2048
-type: application
-version: 1.0.2
-appVersion: 1.0.0
 maintainers:
   - name: evantage
     email: helm@evantage.nl
 annotations:
   catalog.cattle.io/display-name: Evantage Game 2048
   catalog.cattle.io/release-name: evantage-game-2048
+
+# A chart can be either an 'application' or a 'library' chart.
+#
+# Application charts are a collection of templates that can be packaged into versioned archives
+# to be deployed.
+#
+# Library charts provide useful utilities or functions for the chart developer. They're included as
+# a dependency of application charts to inject those utilities and functions into the rendering
+# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+type: application
+
+# This is the chart version. This version number should be incremented each time you make changes
+# to the chart and its templates, including the app version.
+# Versions are expected to follow Semantic Versioning (https://semver.org/)
+version: 1.0.0
+
+# This is the version number of the application being deployed. This version number should be
+# incremented each time you make changes to the application. Versions are not expected to
+# follow Semantic Versioning. They should reflect the version the application is using.
+# It is recommended to use it with quotes.
+appVersion: 1.0.3
diff --git a/charts/hello-rancher/Chart.yaml b/charts/hello-rancher/Chart.yaml
index b95c910..2e6c09b 100644
--- a/charts/hello-rancher/Chart.yaml
+++ b/charts/hello-rancher/Chart.yaml
@@ -1,12 +1,30 @@
 apiVersion: v2
 name: hello-rancher
 description: Hello Rancher demo application, web UI showing scale of containers
-type: application
-version: 1.0.3
-appVersion: 1.0.0
 maintainers:
   - name: evantage
     email: helm@evantage.nl
 annotations:
   catalog.cattle.io/display-name: Evantage Hello Rancher
   catalog.cattle.io/release-name: evantage-hello-ranhcer
+
+# A chart can be either an 'application' or a 'library' chart.
+#
+# Application charts are a collection of templates that can be packaged into versioned archives
+# to be deployed.
+#
+# Library charts provide useful utilities or functions for the chart developer. They're included as
+# a dependency of application charts to inject those utilities and functions into the rendering
+# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+type: application
+
+# This is the chart version. This version number should be incremented each time you make changes
+# to the chart and its templates, including the app version.
+# Versions are expected to follow Semantic Versioning (https://semver.org/)
+version: 1.0.0
+
+# This is the version number of the application being deployed. This version number should be
+# incremented each time you make changes to the application. Versions are not expected to
+# follow Semantic Versioning. They should reflect the version the application is using.
+# It is recommended to use it with quotes.
+appVersion: 1.0.4
diff --git a/charts/nettools/Chart.yaml b/charts/nettools/Chart.yaml
index 50795fe..cf821a8 100644
--- a/charts/nettools/Chart.yaml
+++ b/charts/nettools/Chart.yaml
@@ -1,12 +1,30 @@
 apiVersion: v2
 name: evantage-nettools
 description: A container with network tools on SLE Base Container Image, based on github.com/nicolaka/netshoot
-type: application
-version: 1.0.4
-appVersion: "1.0.0"
 maintainers:
   - name: evantage
     email: helm@evantage.nl
 annotations:
   catalog.cattle.io/display-name: Evantage Nettools
-  catalog.cattle.io/release-name: evantage-nettools
\ No newline at end of file
+  catalog.cattle.io/release-name: evantage-nettools
+
+# A chart can be either an 'application' or a 'library' chart.
+#
+# Application charts are a collection of templates that can be packaged into versioned archives
+# to be deployed.
+#
+# Library charts provide useful utilities or functions for the chart developer. They're included as
+# a dependency of application charts to inject those utilities and functions into the rendering
+# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+type: application
+
+# This is the chart version. This version number should be incremented each time you make changes
+# to the chart and its templates, including the app version.
+# Versions are expected to follow Semantic Versioning (https://semver.org/)
+version: 1.0.0
+
+# This is the version number of the application being deployed. This version number should be
+# incremented each time you make changes to the application. Versions are not expected to
+# follow Semantic Versioning. They should reflect the version the application is using.
+# It is recommended to use it with quotes.
+appVersion: 1.0.4
\ No newline at end of file