Skip to content

Commit

Permalink
feat: update helm samples to use helm3 (#78)
Browse files Browse the repository at this point in the history
* helm3 guestbook

* helm3 blue-green

* helm3 dependencies

* helm3 plugin

* helm3 plugin

* helm3 plugin

* helm3 apps

* helm3 dependency

* helm3 dependency

* helm3 dependency

* helm3 fix readme
  • Loading branch information
mayzhang2000 committed Mar 3, 2021
1 parent 466269d commit 53e28ff
Show file tree
Hide file tree
Showing 8 changed files with 120 additions and 20 deletions.
24 changes: 21 additions & 3 deletions apps/Chart.yaml
Original file line number Diff line number Diff line change
@@ -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"
24 changes: 21 additions & 3 deletions blue-green/Chart.yaml
Original file line number Diff line number Diff line change
@@ -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"
29 changes: 28 additions & 1 deletion helm-dependency/Chart.yaml
Original file line number Diff line number Diff line change
@@ -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
4 changes: 0 additions & 4 deletions helm-dependency/requirements.yaml

This file was deleted.

24 changes: 21 additions & 3 deletions helm-guestbook/Chart.yaml
Original file line number Diff line number Diff line change
@@ -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 changes: 27 additions & 0 deletions plugins/kustomized-helm/Chart.yaml
Original file line number Diff line number Diff line change
@@ -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
4 changes: 2 additions & 2 deletions plugins/kustomized-helm/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
4 changes: 0 additions & 4 deletions plugins/kustomized-helm/requirements.yaml

This file was deleted.

0 comments on commit 53e28ff

Please sign in to comment.