using ks instead of chart

apps/coder/env/k3s-cluster/Chart.yaml

@@ -1,28 +0,0 @@
-apiVersion: v2
-name: coder
-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: "0.0.1"
-
-dependencies:
-  - name: coder
-    version: 2.13.1
-    repository: https://helm.coder.com/v2

apps/coder/env/k3s-cluster/kustomization.yaml

@@ -0,0 +1,8 @@
+apiVersion: kustomize.config.k8s.io/v1beta1
+kind: Kustomization
+helmCharts:
+  - name: coder
+    repo: https://helm.coder.com/v2
+    version: 2.13.1
+    releaseName: coder
+    valuesFile: values.yaml