Skip to content

Commit

Permalink
charts update
Browse files Browse the repository at this point in the history
  • Loading branch information
Evantage-WS committed Dec 8, 2024
1 parent f8274e8 commit 9aa8f78
Show file tree
Hide file tree
Showing 4 changed files with 74 additions and 13 deletions.
13 changes: 10 additions & 3 deletions charts/dvwa/Chart.yaml
Original file line number Diff line number Diff line change
@@ -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.
#
Expand All @@ -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
Expand Down
24 changes: 21 additions & 3 deletions charts/game-2048/Chart.yaml
Original file line number Diff line number Diff line change
@@ -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
24 changes: 21 additions & 3 deletions charts/hello-rancher/Chart.yaml
Original file line number Diff line number Diff line change
@@ -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
26 changes: 22 additions & 4 deletions charts/nettools/Chart.yaml
Original file line number Diff line number Diff line change
@@ -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
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

0 comments on commit 9aa8f78

Please sign in to comment.