Browse Source

feat: update helm samples to use helm3 (#78)

* helm3 guestbook

* helm3 blue-green

* helm3 dependencies

* helm3 plugin

* helm3 plugin

* helm3 plugin

* helm3 apps

* helm3 dependency

* helm3 dependency

* helm3 dependency

* helm3 fix readme
May Zhang 3 years ago
parent
commit
53e28ff20c

+ 21 - 3
apps/Chart.yaml

@@ -1,5 +1,23 @@
-apiVersion: v1
-appVersion: "1.0"
-description: Applications
+apiVersion: v2
 name: applications
+description: Applications
+
+# 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: 0.1.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.
+appVersion: "1.0"

+ 21 - 3
blue-green/Chart.yaml

@@ -1,5 +1,23 @@
-apiVersion: v1
-appVersion: "1.0"
-description: A Helm chart for Kubernetes
+apiVersion: v2
 name: helm-guestbook
+description: A Helm chart for Kubernetes
+
+# 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: 0.1.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.
+appVersion: "1.0"

+ 28 - 1
helm-dependency/Chart.yaml

@@ -1 +1,28 @@
-name: wordpress
+apiVersion: v2
+name: wordpress
+description: A Helm chart for Kubernetes
+
+# 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: 0.1.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.
+appVersion: "1.0"
+
+dependencies:
+- name: wordpress
+  version: 9.0.3
+  repository: https://charts.helm.sh/stable

+ 0 - 4
helm-dependency/requirements.yaml

@@ -1,4 +0,0 @@
-dependencies:
-- name: wordpress
-  version: 5.0.2
-  repository: https://charts.helm.sh/stable

+ 21 - 3
helm-guestbook/Chart.yaml

@@ -1,5 +1,23 @@
-apiVersion: v1
-appVersion: "1.0"
-description: A Helm chart for Kubernetes
+apiVersion: v2
 name: helm-guestbook
+description: A Helm chart for Kubernetes
+
+# 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: 0.1.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.
+appVersion: "1.0"

+ 27 - 0
plugins/kustomized-helm/Chart.yaml

@@ -1 +1,28 @@
+apiVersion: v2
 name: guestbook
+description: A Helm chart for Kubernetes
+
+# 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: 0.1.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.
+appVersion: "1.0"
+
+dependencies:
+- name: helm-guestbook
+  version: 0.1.0
+  repository: file://../../helm-guestbook

+ 2 - 2
plugins/kustomized-helm/README.md

@@ -12,10 +12,10 @@ Use following steps to try the application:
     - name: kustomized-helm
       init:
         command: ["/bin/sh", "-c"]
-        args: ["helm init --client-only && helm dependency build"]
+        args: ["helm dependency build"]
       generate:
         command: [sh, -c]
-        args: ["helm template . > all.yaml && kustomize build"]
+        args: ["helm template --release-name release-name . > all.yaml && kustomize build"]
 ```
 
 * create application using `kustomized-helm` as a config management plugin name:

+ 0 - 4
plugins/kustomized-helm/requirements.yaml

@@ -1,4 +0,0 @@
-dependencies:
-- name: helm-guestbook
-  version: 0.1.0
-  repository: file://../../helm-guestbook