chore: add charts kustomize and plain app

apps/plain-avp/secret.yaml

@@ -0,0 +1,19 @@
+# Carsten Lenz
+# 2023/03/07
+#
+
+apiVersion: v1
+kind: Secret
+metadata:
+  name: avp-demo-plain-secret1
+stringData:
+  foo: <path:product-team-example/data/hello#foo>
+---
+apiVersion: v1
+kind: Secret
+metadata:
+  annotations:
+    avp.kubernetes.io/path: "product-team-example/data/hello"
+  name: avp-demo-plain-secret2
+stringData:
+  foo: <foo>

charts/avp-demo/.helmignore

@@ -0,0 +1,23 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*.orig
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/

charts/avp-demo/Chart.yaml

@@ -0,0 +1,36 @@
+# Carsten Lenz
+# 2023/03/07
+#
+
+apiVersion: v2
+name: avp-demo
+description: A AVP Demo Chart
+
+sources:
+  - https://github.com/carslen/avp-demo
+
+home: https://github.com/carslen/avp-demo
+
+maintainers:
+  - name: Carsten Lenz (carslen)
+
+# 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.
+# It is recommended to use it with quotes.
+appVersion: "0.1.0"

charts/avp-demo/templates/secret.yaml

@@ -0,0 +1,19 @@
+# Carsten Lenz
+# 2023/03/07
+#
+
+apiVersion: v1
+kind: Secret
+metadata:
+  name: avp-demo-helm-secret1
+stringData:
+  foo: {{ .Values.secrets.path }}
+---
+apiVersion: v1
+kind: Secret
+metadata:
+  annotations:
+    avp.kubernetes.io/path: {{ .Values.secrets.annotated }}
+  name: avp-demo-helm-secret2
+stringData:
+  foo: <foo>

charts/avp-demo/values.yaml

@@ -0,0 +1,7 @@
+# Carsten Lenz
+# 2023/03/07
+#
+
+secrets:
+  path: <path:product-team-example/data/hello#foo>
+  annotated: "product-team-example/data/hello"

charts/avp-demo2/.helmignore

@@ -0,0 +1,23 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*.orig
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/

charts/avp-demo2/Chart.yaml

@@ -0,0 +1,41 @@
+# Carsten Lenz
+# 2023/03/07
+#
+
+apiVersion: v2
+name: avp-demo2
+description: A AVP Demo Chart - with dependencies
+
+sources:
+  - https://github.com/carslen/avp-demo
+
+home: https://github.com/carslen/avp-demo
+
+maintainers:
+  - name: Carsten Lenz (carslen)
+
+# 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.
+# It is recommended to use it with quotes.
+appVersion: "0.1.0"
+
+dependencies:
+  - name: mariadb
+    version: 11.0.10
+    repository: https://charts.bitnami.com/bitnami

charts/avp-demo2/templates/secret.yaml

@@ -0,0 +1,19 @@
+# Carsten Lenz
+# 2023/03/07
+#
+
+apiVersion: v1
+kind: Secret
+metadata:
+  name: avp-demo2-helm-secret1
+stringData:
+  foo: {{ .Values.secrets.path }}
+---
+apiVersion: v1
+kind: Secret
+metadata:
+  annotations:
+    avp.kubernetes.io/path: {{ .Values.secrets.annotated }}
+  name: avp-demo2-helm-secret2
+stringData:
+  foo: <foo>

charts/avp-demo2/values.yaml

@@ -0,0 +1,10 @@
+secrets:
+  path: <path:product-team-example/data/hello#foo>
+  annotated: "product-team-example/data/hello"
+
+mariadb:
+  auth:
+    database: foo<path:product-team-example/data/hello#foo>
+    username: "foo"
+  commonLabels:
+    foo: "<path:product-team-example/data/hello#foo>"

kustomize/kustomization.yaml

@@ -0,0 +1,8 @@
+# Carsten Lenz
+# 2023/03/07
+#
+apiVersion: kustomize.config.k8s.io/v1beta1
+kind: Kustomization
+
+resources:
+  - secret.yaml

kustomize/secret.yaml

@@ -0,0 +1,19 @@
+# Carsten Lenz
+# 2023/03/07
+#
+
+apiVersion: v1
+kind: Secret
+metadata:
+  name: avp-demo-kustomize-secret1
+stringData:
+  foo: <path:product-team-example/data/hello#foo>
+---
+apiVersion: v1
+kind: Secret
+metadata:
+  annotations:
+    avp.kubernetes.io/path: "product-team-example/data/hello"
+  name: avp-demo-kustomize-secret2
+stringData:
+  foo: <foo>